I still don't understand what you're trying to build.
If it's about protecting access with a password the transformation should be easy from one direction, and practically impossible from the other (such as with hash functions);
If it's a puzzle that will take the user some time to solve, probably a program can solve it very quickly. Is that what you're looking for?
The second one
it’s a teamwork thing
I’m testing out a system where you need 4 different people to view a project and each person gets their own part of the code, then it’s all assembled into one code and that gets decoded
The code for doing that is done ( I even made a reimplementation the the “user id” block for this ) but making the code for separating the string into 4 parts is where I’m drawing a blank
@cookieclickerer33 wants a way to hide something ("Opuscating" [sic]) in their code to make it harder for someone to read it. Unfortunately, I think this isn't allowed.
That project was for a fun kind of thing. They want to make their code un-readable, which isn't allowed. It seems their going to do it anyway, so I wouldn't be surprised if they got a warning or got banned for doing this.
IIRC, it is allowed but like annoying/frowned upon to purposefully make your code unreadable-- while the bit that is not allowed is making your project unable to be remixed/edited through methods like a self-destructing project.