Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
i just realized why aint the clouds morphable, that would save space..
2.0
Offline
SirJosh3917, Br0k3n, KingFudge, Fastmapler, shadowda, Stubby, Badoosh, some woman, Falk, Era, TSF14, CREASTEDFACE, Schlog, zioxei, Krosis, skullz17
fog too
Offline
also pipes, so it well only be 2 blocks but they can be morphable and add more pipe pieces like 4 way pipe and corner.
2.0
Offline
Grass or snow decors could be morphable too.
( ͡° ͜ʖ ͡°)
Offline
The issue is that, if we turn things morphable now, everything will be on morph 1 by default, so it'd ruin a ton of levels.
The alternative is running a bot to change all relevant blocks in all worlds into their proper morphs, but this takes a long time and isn't particularly safe.
No u.
Offline
The issue is that, if we turn things morphable now, everything will be on morph 1 by default, so it'd ruin a ton of levels.
The alternative is running a bot to change all relevant blocks in all worlds into their proper morphs, but this takes a long time and isn't particularly safe.
or it could be different id as they are, and just put the morph thing without have to transform the morphables in meta-ids
Offline
The issue is that, if we turn things morphable now, everything will be on morph 1 by default, so it'd ruin a ton of levels.
The alternative is running a bot to change all relevant blocks in all worlds into their proper morphs, but this takes a long time and isn't particularly safe.
Not neccesarily true.
if pipes have 2 id's you can have the first id translate into firstid:0 on first worldload and the second id into firstid:1
i really don't see a problem here
Offline
Not neccesarily true.
if pipes have 2 id's you can have the first id translate into firstid:0 on first worldload and the second id into firstid:1
i really don't see a problem here
They would have to modify all levels containing them, which isn't reliable.
Why not make it so they show up in the UI like morphable, while being actually regular blocks? You would have to click several times in the bar to cycle through the different blocks, instead of placing the same block several times
Offline
They would have to modify all levels containing them, which isn't reliable.
And why exactly... it doesn't matter whter it sais id1,id2 in the db
if you change it on worldload it'd work... theres no nee to crawl through the whole database now.
Offline
And why exactly... it doesn't matter whter it sais id1,id2 in the db
morphables have 2ids: the block ID and the morphable ID, turning a block into a morphable one means you have to turn an ID into 2 new ones, which also means shifting all the bytes after the 1st to-become-morphable block, one mistake and the worlds become corrupt.
if you change it on worldload it'd work... theres no nee to crawl through the whole database now.
The check would be done several times on the same world (every time it is loaded), which isn't particularly efficient, otherwise why not
Offline
Pages: 1
[ Started around 1715987387.2285 - Generated in 0.031 seconds, 11 queries executed - Memory usage: 1.54 MiB (Peak: 1.7 MiB) ]