Thanks for the interest, I'm glad someone will be able to use this!

You did not, in fact, fix the bug (we were both missing a wildcard character... doh!), but I fixed it now. I did include your idea about the finishing text, so you're credited inside the CFG.

New version only keybinds MOUSE2 in normal play and the editbind for MOUSE1.

Oh ok, thanks. I'm not exactly an expert at CubeScript, but I tried my best. I dunno if you saw it but I made it so that the bindings would be reversed to normal at the end.
So does that mean the teledest gets deleted now btw? I couldn't do it because it treated 1 as the angle...

You took many fixes I made... Also, why are both the teleport and teledest assigned to the same button? That's not exactly fun or useful...
You even took out my showgui fixes! Please update this with MY version, ok?
You created some typo bugs hehe, also fixed 'em. See for yourself :P

Edited by Quin: Please refrain from inflammatory remarks. Also note that while your intention may be to help, you are creating a tense atmosphere with the way you present yourself. If you truly are an amateur, perhaps you should be trying to improve your own work, before 'correcting' others.

You've introduced new bugs into the script with your version. I'm not going to use flawed code, nor will I put in your false statements; you have to be in SP for the final trigger to work, so your statement about "No need to backup your binds" is just wrong. As I suggested on the forum, this could used for DMSP, not just SP.

It is very important for level design that the "portals" are held together. If the player can put the dest and the port in different places it makes it much harder to make good levels. Also, we want to rebind as few keys as possible. Hence, just MOUSE2 and the editbind for MOUSE1.

If you can't even follow the "why"s of my little script (and lets face it, it's 123 easy, I'm not doing anything hard here), perhaps you should restrain from trying to correct me. All you did in your "fixes" was rearrange what I had previously put down, effectively breaking what little I had done.

---

I did update the scripts with one small addition: the teledest will now be rotated 180 degrees, so it's less likely to be facing a wall. Not an ideal solution, but it helps.

Edited by Quin: Please refrain from inflammatory remarks.

Everyone has their opinion, and I respect that. Answering to your reply:

-I've never tried it on DMSP or multiplayer... always on SP. Hence, that "showgui portal" wasn't working (I don't even know if it works anywhere, I doubt it). So I had to create an invisible trigger on the playerstart to make it work. So this ain't a "minor fix".
-I didn't know you had a forum thread.
-In my opinion I don't actually like having both the teleport and the teledest together. Why? Because if the player is distracted he'll pass the old teleport, appear at the new teledest and then pass through the new teleport. Also don't forget that you can bind it in any way you want, depending on the type of portal level you're intending to do. It doesn't mean that it's fun or helpful. Hell, you can even change the bindings again in SP to make some sort of "level 2" inside the same level. One can make lots of portal variations.
- I try to fix it for the most-usable game mode, SP, and you say I'm breaking everything apart. Yes, the small letter typo is a very minor fix, but "every bit counts".

Edited by Quin: Please refrain from inflammatory and inaccurate remarks.

No, it's just like you said.

Welcome to Quadropolis (as seen on the front page)
User's Guide (as linked from that article)
and not to forget
Packaging Guide (to make life easier on other users)

Sorry old chap, I guess I've taken it a bit too far. Now for more answers...
-There is no "superior" content. It's just a conception from 2 or more different people, despite the differences.
-I guess you don't know what a smiley and a joke are, lol. Probably a somewhat agressive phrase to start off, even for a joke, so I apologize.
-No, I didn't call your script useless. I just said the way you placed the teleport and teledest (glued together) isn't exactly the best way. I would still prefer the 2-button way of placing them.
-Nope, I also didn't demand, I just said "please". You probably didn't see the smiley here too, hehe. Also I shouldn't have said "MY" with those big letters :P
-You've got your fair amount of namecalling already, so it's even ;)
-I'm using Assassin edition plus my SEx mod. It won't do any difference though. As I've said I only tested it on SP and the showgui command wasn't exactly working, unless I typed it on the console or assign a trigger to it like I did in that Bug-fixed version of mine.
-As I've said, I didn't know you had a forum thread.
-Yes they are different opinions and they should be accepted. You also need a brain exam, I see :P Yes I'm joking again.
-What breakline? I tested both maps and they were working just fine.

Just a final note here: Your sarcasm really didn't help at all. I guess you need to realize "every bit counts" and that's what really matters. Just don't be mad at me; I respect your work, a lot. But you need to respect the other's work too. So it's true I made a mistake, everyone does, but I learned from it. Also note I'm no professional at CubeScript, so mistakes can often occur.
I also have to apologize to the good ol' admin, Quin. He's doing a good job and others sometimes make it harder for him. Cheers to both ;)

Definitely agree that we're making Quin work more than he should. I apologize for my part in that.

Real quick, here's the explaination for the breakline:
In the first version I put up, I had used a breakline after binding MOUSE2 to jump into editmode: my logic was that it would be easier to read and edit. Turns out that even though all the binds and editbinds are nested inside the appropriate quotes, Sauerbraten will go ahead and run this newline as if it was freestanding. In a nutshell, the gui was going ahead and doing stuff that the user hadn't confirmed. It took me about an hour of playing around with the editor to actually figure that out: it was an exceptionally frustrating hour, and it was therefore extra upsetting to see that frustration return.

I really can't suss out what the difference between our showguis is. I guess we'll just have to assign it to some unusual bug, I have not been able to find a way to reproduce it not working. Curious.

It's alright guys. Just remember we're here to share, collaborate, and learn. I've helped shape Quad into a great place for that, and I appreciate you guys understanding how much work I really do put into making it that way :)

This map is a classic example of people's imaginations running away with them, and their desire to make something Sauerbraten isn't meant to do, actually work. It's understandable people get passionate (to the point of getting into a fit, just like a relationship, huh?) about it. Don't lose that innovative spirit, you guys should be helping each other, not arguing :P

I like what you have there: it'll be fun to see what I can do with those.

Yes, flinging is out of reach until the player can run faster... I've been meaning to bring this up for a while. Definitely for Eisenstern, definitely not for the FPS, run speed should start slower and increase over a period of time, barring external events. In a FPS it makes sense to stay at a sprint: for a RPG it makes more sense to jog and work up to a sprint. Should such a mechanic become available, it could then be "uncapped" so to speak, to allow for portal-based momentum buildup.

As to a portal gun, I'm not really sure. I'm running into problems by not having "unportalable" surfaces- this could pose difficulties especially for a gun (at least in editmode I can toss up a noclip or something, even if it only halfway solves the problem).

---

I made a third concept map, this time feebly attempting to force the player to look up (which, as pointed out in Portal's commentaries, is dang hard). It also introduces the ability to place both portals once in editmode. I hope people like it, it's the most original map so far (I say this somewhat self-mockingly...)

The real problem with duplicating the mechanics and physics of a portal is that some flings in the game are executed in a manner which excludes the possibility that they could be used in C2/variants thereof, I.E. mid-fall portal creation. You'd lose all your momentum due to editmode.

One additional issue is the orientation of a portal. Portals on ceilings and floors would look awfully silly in C2 or variants. :)

To my knowledge, these are not things easily worked around.

But I'm definitely including a portal-like puzzle in the SP map I'm working on!

Which is why I want to write the code that would allow this kind of mechanic for real. As I no longer develop for Sauerbraten, I would most likely be doing this in Blood Frontier though (somewhere along the line, depends on interest).

Would you mnd pasting your code into a commnet, I'd be quite interested to see your method. Oh, just for reference, here's the current setup (as in portal3):

guibutton "OK" "bind MOUSE1 [attack]; bind MOUSE2 [edittoggle; paused (= $paused 0)]; editbind MOUSE1 [editdrag; entfind teledest * 1; delent; newent teledest 1; entpush -1; entproperty 0 180; entcancel; entfind teleport 2; delent; newent teleport 2; paused (= $paused 0); edittoggle]; editbind MOUSE2 [editdrag; entfind teledest * 2; delent; newent teledest 2; entpush -1; entproperty 0 180; entcancel; entfind teleport 1; delent; newent teleport 1; paused (= $paused 0); edittoggle]"

Remember, it has to be all one line, or funny things will happen and go wrong.

It's messy because you edittoggle twice before you attack. This is what I have my Sauer bound to currently, but I'll be moving this elsewhere before I play online again, 'cause I don't want to see messages about being unable to edittoggle in non-coopedit modes. :)

bind mouse1 [edittoggle; if (= $modifier 1) [sleep 50 [portal1] ] [edittoggle; attack]]

alias portal1 [
gridreturn = $gridpower
gridpower 2
entfind teledest * 1
entfind teleport 2
delent
editdrag
newent teleport 2
entcancel
newent teledest 1
entpush -3
entproperty 0 180
entcancel
gridpower $gridreturn
echo reached
edittoggle
]

bind mouse2 [edittoggle; if (= $modifier 1) [sleep 100 [portal2]] [edittoggle; zoomit] ]

alias portal2 [
gridreturn = $gridpower
gridpower 2
entfind teledest * 2
entfind teleport 1
delent
editdrag
newent teleport 1
entcancel
newent teledest 2
entpush -3
entproperty 0 180
entcancel
gridpower $gridreturn
echo reached
edittoggle
]

The basic idea is that when you hold the modifier key, the mouse1 and mouse2 become the portal gun buttons. There's a noticeable flicker into editmode, unfortunately, but not when you shoot (except that rockets and nades disappear if you click instead of holding).

i had the same problem. play the portal again and somewhere you will be asked if you want to keep the keybindings. There you can change it back.