Blockland Forums > Suggestions & Requests
New "brick": Portal
Trader:
Wow, lame. First of all, it would be the player datablock ::onCollision, because it's the player colliding with the brick. Second, collision portal stuff is outdated. I would prefer a key system. You walk up to a portal, 'insert' your key, and it opens a menu of all the available portals. Then you could choose where you want to go. Some portals could be restricted to admins/super admins only.
-=>RR<=-MasterCE:
--- Quote from: -=>RR<=-MasterCE on March 07, 2007, 08:22:54 PM ---ifonly I knew Retails brick commands...I'll do .dump on one later, but if there was an oncollision, it's go something like this, but this i'm sure won't work because i'm just making up an example:
--- Code: ---function brick::oncollision(%this,%col) {
if(%col.namebase && %this.isteleporter) {
%col.settransform(%this.otherendtransform);
}
}
--- End code ---
--- End quote ---
When I post a script like that, I never mean for it to EVER work I'm just giving a rough example on how it should work. I f'ed up in posting and didn't say this in the post :/
Ephialtes:
fxDTSBricks do not have a collision callback so there is no way of knowing when you're touching one - without a little haxx.
stevey1000:
If anyone has teh hax, It'd be you Ephi. :3
Grimsy:
--- Quote from: Flea on March 07, 2007, 06:52:10 PM ---Basicly you want id teleporters -.-
--- End quote ---
More like ID PORTALS, which you can see through to the other side. Observer:
--- Code: ---0 = player, | = portal, . = nondescript floor
An examplatory useage of portals:
...0...| |.......
To the player, this would look more like thus:
...0...|.......
Or perhaps like this (if the thing is advanced enough):
...0...........
--- End code ---
Of course, it could have different modes (auto-connect-to-ID, portal gateways, etc.), but still, the main thing this would add is the view to the "other side" of the teleportation whatsit.