raocow's talkhaus

HenryRichard wrote:I might go next if no one else does - I won't be able to work on it for a few hours though.

How's your section going?

any updates on this?

The sections feature has been stubbornly broken up until 1.3.2; every time I thought I fixed it the blasted thing ended up still not working for someone. Once the 1.3.3 update is ready I'll copy it over to onedrive. In the meantime, you can work around it by leaving the sections undefined and just ...

sections={2:1, 3:5, 4:99999} Should make the layer appear in sections 2, 3 and 4. Undefined indexes in lua tables return nil, so as long as the index is assigned any value besides nil it'll count. That said, it's clear now that index-based is relatively unintuitive and suddenly changing the argumen...

Ah, sorry, I forgot to update the documentation. The former implementation wouldn't work no matter what I tried so in the latest version sections are based on index instead of value; as long as sections[2] is a non-nil value it'll work. iirc the proper syntax is {2:1}. I don't understand the explan...

I need help, I'm using ParalX and the sections (sections = {2}) argument straight up doesn't work, the paralax graphics I only want to show in a section section only show up in section 1. am I using an outdated version of ParalX? local paralX = loadAPI("paralX"); local pnpc = loadSharedAPI...

I admit that I haven't played the level yet (waiting for my turn), but maybe the higher difficulty of the relay would be enough make up for its shorter-than-average length. After all, we still have five screens left. I say we wait until after everyone has made a screen, and if we still think it's t...

did we ever fix the problem of the screen being too tall?

MECHDRAGON777 wrote:Bump

Anything on your section?

???????????????? the hell on my end the level has the filter blocks removed...? Oh, wait, nevermind. you only removed the filter in your section, I thought you also changed the blocks in my section as well. sorry for the misunderstanding! I fixed the issues with my section: https://www.dropbox.com/...

Pyro wrote:dangit did i not upload the right thing...? i thought i removed the filter blocks

edit: try now, i updated the dropbox link

it's still the same?
all the demo filter blocks are still demo filter blocks,
and as far as I can tell the Lua files aren't any different.

Pyro wrote:updated

you should probably update the OP too, stuff is probably going to get disorganized soon

I couldn't find the difference between the files you uploaded and the files I uploaded?

I'm Done!
https://www.dropbox.com/s/c9iufsbpwyq3g ... l.zip?dl=0
it's pretty short though, maybe I could split my section with someone else?

Oh, I'm gonna go next!

SAJewers wrote:ping

we should make a list or something of who's getting what screen

SAJewers wrote:It's first-come-first-serve; whoever claims the next spot will get it.

So I can claim section 4 right now?
can I do that?

Did we ever get around to splitting the level so far into two sections?

does anybody mind if I redo my section after Mechdragon is done with their section? I feel like I did A pretty shoddy job on it.

Of course, I'll be more than willing to participate in any relay things we might be doing

eh, I gave up on making levels

I need help, The data class "bums" is always 1 when I load the level local encrypt = API.load("encrypt") local myData = encrypt.Data(Data.DATA_LEVEL, true) if myData:get("bums") == nil then myData:set("bums",0) myData:save() end function onLoad() if myData:get...

I'm not sure where to put this, so I'm putting this here:

I downloaded the newest version of the A2XT base game off of the onedrive, and the raocow player character has some weird offset issues

S1eth wrote: This code only does anything if you are inside the block rather than touching the block, for example if you use block id 447 (cloud, go through from below)

Oh, okay. is there any good way to check if you are touching a not-cloud block?

I'm unsure what I'm doing wrong? Do I not have the latest version of colliders? local colliders = loadAPI("colliders"); function onLoop() if (colliders.collideBlock(player,1)) then player.speedY = -10 end end What's happening that's wrong? This should push the player up when they touch a ...