#Decal Registry <staticMover/>

81 messages · Page 1 of 1 (latest)

ornate sphinx
#

I wanna know, what is the unit of each number?
I have 3 decals sized 64x64, and I set:
<staticMover x="-32" y="-32" width="64" height="64"/>
but not all of them are attached to the switchgate

lament python
#

almost certainly pixels

ornate sphinx
#

pixels... What is the starting point of the axis?

ornate sphinx
lament python
#

uh probably? idk what exactly you mean by that, but in celeste X+1 is more right and y+1 is more down

ornate sphinx
#

So theoratically...

#

<staticMover x="-32" y="-32" width="64" height="64"/>
should be right for a 64x64 decal?

lament python
#

from the looks of things the static mover attribute doesn't care about the size of the decal

ornate sphinx
#

huh? then how do I know where the collision box I set is?

#

I can't literally see it, lol

lament python
#

I think the x and y point it to what the decal should attach to, and the width/height tell it how big the thing it's attaching to is?

ornate sphinx
#

Huh?

#

I don't think so?

#

The decals are the same size putting on a same place

#

And staticMover is set the same

#

only one of 3 decals work

lament python
ornate sphinx
#

I'm not either...

#

I'm no coder

ornate sphinx
#

I don't get it

#

x and y is my value

#

What is (Int) X and (int) Y?

lament python
#

okay I see what it's doing now but I think it matches how you originally thought it work catplant

#

can you show the 3 different setups you have and which one works/doesn't work

ornate sphinx
#

Mm...Wait a sec...

lament python
#

static movers are for attaching different entities together e.g. spikes attaching to zip movers/swapblocks/dashblocks are considered by code to be static movers

ornate sphinx
#

but... isn't it Decal Registry?

#

i wanna attach my decal to the switch gate

lament python
#

oh right there's a switch gate somewhere

lament python
ornate sphinx
#

Hmm, alright, lol, I'll show you when I'm back at my computer

lament python
#

yh, your static mover is in a solid, and it doesn't like that

ornate sphinx
#

wait...

#

static mover shouldn't be inside the solid?

lament python
#

don't think so

ornate sphinx
#

So. I checked the bee map in SJ...

#

the staticMover is x=y=1

#

and the size is 16x16

#

according to your suggestion, the collision box should be right next to the switch gate?

lament python
#

yes - but selecting a decal in the editor will only show the decal's selection rather than the static mover's hitbox

ornate sphinx
#

this is it tearing apart

ornate sphinx
#

the little circle was attached to the switchgate

#

all of them has the same staticmover parameters: x=-32, y=-32, w=h=64

ornate sphinx
lament python
#

that is a good question catplant

lament python
# ornate sphinx hmm

okay I think debug hitboxes might show you where the static mover is getting placed (celestetas doesn't seem to at all)

ornate sphinx
#

the '~' button?

lament python
#

if that opens the debug menu then yh

ornate sphinx
#

I'll have a check...?

#

Hmm

#

no nothing

#

The rectangle one is switchgate

#

not the decal's

#

Only the circle went up, LOL

#

This is weird

lament python
#

(wouldn't change the inner circle since it's working tho)

ornate sphinx
#

Alright

#

I'll try making a 8x8 collision box now

#

Nah

#

Still the circle works

ornate sphinx
#

Turns out that the animation parameters can be controlled by setting the root folder, but not staticMover

#

the three pics are circle.png, wheel/wheel.png, and crossbar/crossbar.png

#

I can set the animation using only one line

#

But when it comes to static mover I have to set the root folder, wheel/ folder and crossbar/ folder