validate soul-event-5
(gun) parameters
#127
Labels
datapack
Issues pertaining to the datapack
resourcepack
Issues pertaining to the resourcepack
validation
validation that preexisting features are functioning and appear as clean as possible
run the soul event (individually and during a boss fight) and analyze how the following properties feel:
bullet/flower sizes
currently when we summon a bullet/flower (healer), they summon as-is with no animation. they may be a bit small though. in order to increase their size we'd need to add a scale-up animation where they get bigger a couple frames after being shot.
we'd want to increase their size if it's too easy to dodge the bullets / too hard to catch the flowers.
we already do this scale-up animation for the ACT button:
omega-flowey-minecraft-remastered/datapacks/omega-flowey/data/entity/function/soul/soul_5/act_button/summon.mcfunction
Lines 1 to 2 in eb19a44
gun rotation speed
the gun rotates towards the crosshair at some speed.
omega-flowey-minecraft-remastered/datapacks/omega-flowey/data/entity/function/soul/soul_5/indicator/loop/shooting/rotate.mcfunction
Lines 45 to 49 in 59860ab
this can be adjusted now (staying linear), but will need to be reconsidered affected if/when #131 is worked on
gun rotation speed post-saved, flower speed, flower spawn radius
we could change these values post-SAVED so that the flowers are easier to catch. maybe not necessary if the flower sizes are increased
general score parameters
there's only two for this soul event:
omega-flowey-minecraft-remastered/datapacks/omega-flowey/data/entity/function/soul/soul_5/reset_scores.mcfunction
Lines 1 to 4 in c969aa8
really these should be fine but i'm listing them anyway just in case.
soul.indicator.bullets.total
is definitely good since the gun in Undertale shoots bullets in tripletssoul.executor.clock.length
was calculated by counting how many frames until the player is sent back to the Flowey arena if they don't grab the ACT button.soul.executor.clock.length
, and likely should stay that way)The text was updated successfully, but these errors were encountered: