Author Topic: Brick experimentation  (Read 1010 times)









Special thanks to Sycrone and Althar

Made with the .setDatablock function on bricks

for example,

package BrickPackage
{
function fxDTSbrick::OnActivate(%brick)
{
Parent::OnActivate(%brick);
%brick.setDatablock("brick1x1Data");
}
};

ActivatePackage(BrickPackage);









What is this I don't even...

10/10 would be confused again.

For all who don't know explained in simple terms
I assume
Took a default build, used a magical program to change the look of each brick to that of another brick immediately.

Am I right?

I wonder what the hell I'm looking at. ._.


For all who don't know explained in simple terms
I assume
Took a default build, used a magical program to change the look of each brick to that of another brick immediately.

Am I right?
No, just a script,

-snip-
Special thanks to Sycrone and Althar

Made with the .setDatablock function on bricks

for example,

package BrickPackage
{
function fxDTSbrick::OnActivate(%brick)
{
Parent::OnActivate(%brick);
%brick.setDatablock("brick1x1Data");
}
};

ActivatePackage(BrickPackage);







You could also use a for() loop for this to do all the bricks in the server, without a package.

Somebody get me the GIF where the dudes head is reeling away from the computer, and goes so far out it goes into space.

what are you smoking willis