Quote from TeamSpen210 on August 6, 2015, 5:57 pm

You could do that using just entities. Put the button wherever you want. Then at each dead-end put another copy of the button where you want it to appear. Change the classname to point_template, and it'll be positioned correctly for you. Put the name of the real button in all the teleports. Then make a logic_case, and for each teleport add a different case output to trigger the Telepor input. Then just send the logic_case a PickRandom input onMapSpawn.

Quote from KyloX on August 7, 2015, 1:03 am

TeamSpen210 wrote:

You could do that using just entities. Put the button wherever you want. Then at each dead-end put another copy of the button where you want it to appear. Change the classname to point_template, and it'll be positioned correctly for you. Put the name of the real button in all the teleports. Then make a logic_case, and for each teleport add a different case output to trigger the Telepor input. Then just send the logic_case a PickRandom input onMapSpawn.

The thing is, I want some of the dead-ends to be more detailed, some would have specific mechanics (like 2 dead-ends are connected by linked portals) and one of the dead-ends is the actual exit (find the 2 switches and the exit). Plus logic_case only has 16 spaces and there is 23 dead-ends.

While looking and playing around with the scripts, I think it is possible to do it with scripts, but encountering errors and don't fully know what is the problem.

Quote from HMW on August 22, 2015, 5:09 am

You are correct about GetAngles and SetAngles. These two functions are for retrieving and setting the angles of an object, respectively.

GetAngles returns a vector (just like GetOrigin) that contains the pitch, yaw and roll components.
SetAngles is a little bit different: it expects three parameters, one for each of the pitch, yaw and roll components.

For example, you can transfer the orientation of one entity to another like so:

Code: Select all

local angles = first_entity.GetAngles()
second_entity.SetAngles(angles.x, angles.y, angles.z)

I have updated my script to also look at the orientation of each entity, and maintain those orientations for each position, after swapping the entities. If you don't feel like messing around with GetAngles and SetAngles yourself, then feel free to use this script. [spoiler]But note that "messing around" is also commonly referred to as "learning" [/spoiler]

shuffle_ents V2 Change notes
[spoiler]I changed the name of the "main" function to "shuffle", to better indicate what it does.

The script now also records the orientation (angles) of each entity and applies them to the other entity that is moved to that position. The find_positions and shuffle_ents functions are modified to enable support for this. Instead of passing just location vectors, they now use composite objects that contain both a location and orientation (angles).

For some entity types, setting the proper starting angles in the map can be slightly tricky. For example, in the test map, I could not set the angles on the func_brush objects directly. (I tried adding an "angles" property outside of smart edit, but it just gets ignored.) So instead, each brush is attached to an info_target entity and the script is told to move these info_target entities. Rotating an info_target in Hammer does not set the angle unfortunately, so you have to edit the "angles" property directly. (There are controls for it in the top right corner of the properties window.)[/spoiler]

Quote from KyloX on September 20, 2015, 5:06 am

Well most of my is map is complete and now I started to tweak with the script you gaved me.
Though I keep getting this error:

AN ERROR HAS OCCURED [the index 'GetName' does not exist]

CALLSTACK
*FUNCTION [shuffle()] shuffle_ents.nut line [60]
*FUNCTION [main()] InputRunScript line [1]

The script doesn't pick up the names, from what I understand and changing names doesn't fully work. Could this be that it doesn't fully pick up instances names (which is probably the case), because well... they just become the world.

Edit: This is becoming a major problem, didn't expected to run into this wall. Is there even a possibility to move instances? point_template doesn't work on it, output SetParent as well.
A painful procedure I see is to make everything to a brush so that it would have names and than move it around, but that may cause some lighting issues as brushes aren't keen on having good lighting.

Any suggestions anyone?

Quote from KyloX on September 26, 2015, 6:56 am

This problem really bursted my bubble as basically I have to throw the instance idea to the trash bin (more or less) and have to find different alternatives.

What I have tried:
Tried making everything movable in the instance, making world brushes to func_brushes and changing some props. The script than started to work, but the lighting is quite horrible (especially as func_brushes lighting likes to turn 90 degrees for some reason).
Other solution was using Propper, making the rooms world brushes to a prop. The lighting is a lot different from making it into a func_brush, but it hardly catches any, it is just plain lighting. Though that what I expected after turning it into a prop...

Would be nice to hear some extra suggestions from other mappers.