EDukeWiki - User contributions [en]

Music

2013-01-03T15:01:49Z

Hank:

'''music''' <num> <x1> <x2> <3> <4> <5> <6> <7> <8> <etc>

Sets up music to be played during levels depending on how <num> is used, and how many levels there are.

EXAMPLE:

<num> - 0 (This will mean that only <x1> and <x2> apply, <x1> being the music for the title screen, and <x2> being the music for the end.)
<num> - 1-4 (This really depends on how many episodes you have, you don't really need to put four 'playlists' if you dont have four episodes.)

<1-etc> - TEMP.OGG (This is the music file to be played during whatever level number it applies to.)

EXAMPLE2:

'''music''' 1 E1M1.mid E1M2.OGG E1M3.mid E1M4.mid

(To be played on episode 1, levels one thru four.)

See also [[definevolumename]], [[definelevelname]]

NOTE: supports MIDI, OGG and FLAC.

[[Category:Duke3D 1.3/1.5 commands]]
[[Category:Sound manipulation]]

Category:Editing Music and Sound Effects

2013-01-03T14:30:14Z

Hank: /* Adding Your Own Music and SFX */

User talk:Hank

2012-11-23T14:44:24Z

Hank: /* Mapping Guide */

== Mapping Guide ==
I just thought I'd let you know that the original intent of the mapping sections was to copy [http://dukertcm.com/knowledge-base/downloads-rtcm/duke3d-faqs-build/mpfqdn21.zip Jonah Bishop's MapFAQ v2.1] and then improve that, but everyone involved got too lazy to continue the copypasting. This may save you the trouble of writing your own instructions.

Thanks for the good work.
-[[User:Hendricks 266|Hendricks266]] ([[User talk:Hendricks 266|talk]]) 21:54, 6 March 2012 (PST)

Hey Hendricks266!
Not sure how this works, or if you even get the reply.
There is a clause below the editor stating "You are promising etc." and it also refers to the FAQ to be quite old. So, since I am mapping, I am going through the process of checking this area of the wiki. Yet, if copy and past is good enough, I will later on continue on.

Best
Hank

I added another section for 'invisibility' on the beginners section, with a minimal introduction of F8 in 2D mode.
Something went wrong with the entire page format, so I re-saved the page and left the info itself untouched.
Best
Hank

Category:Editing Working with Sprites

2012-11-22T23:07:22Z

Hank: /* Working With Sprites */

Tic

2012-06-01T03:13:06Z

Hank:

A '''tic''' is each time unit in-game. By default 1 second equals 30 tics.

From the original source code:
// this used to be TICRATE/GAMETICSPERSEC, which was 120/26 = 4.615~ truncated to 4 by integer division
#define TICSPERFRAME 4
#define TICRATE 120

Video setup

2012-05-08T01:01:34Z

Hank: /* Renderer Setup */

The '''''video setup''''' menu is used to adjust several aspects of the game's video display.

==Common Settings==

===Resolution===
:'''''Resolution''''' allows you to select the screen resolution. Use the arrow keys to dial through all available screen resolutions.

===Renderer===
:'''''Renderer''''' allows two render options, Software or OpenGL. There are in fact three [[rendmode|renderers]] in the game which can be toggled with the [[console commands#setrendermode|setrendermode console command]].

===Full Screen===
:'''''Full Screen''''' is a toggle for '''Yes''' (Full Screen) or '''No''' (Windowed).

===Color Correction===
:'''''Color Correction''''' opens to the the following sub-menu:
:*'''''Gamma''''' is a slider to adjust the [[Wikipedia:Gamma_correction|gamma]] of the display.
:*'''''Contrast''''' is a slider to adjust the [[Wikipedia:Contrast_(Vision)|contrast]] of the display.
:*'''''Brightness''''' is a slider to adjust [[Wikipedia:Luma_(video)|brightness]] of the display.

==Software==

===Pixel Doubling===
:'''''Pixel Doubling''''' is the correct terminology for the '''''Detail''''' option in the original game's option menu, with '''Off''' corresponding to High Detail and '''On''' to Low Detail. When enabled, this setting cuts the amount of detail on screen in half by drawing the game viewport at half the current resolution then doubling the pixels from 1x1 to 2x2. This option only appears for the Classic renderer and is recommended to be '''Off''' at all times unless the hardware you are using is incredibly weak making this a necessity.

===Renderer Setup===
:'''''Renderer Setup''''' when in the 'Software' mode opens to the the following sub-menu:
:*'''''Aspect Ratio''''' is an adjustment for the selected screen resolution. '''Auto''' is recommended for most systems. Other options are '''Old Reg'''ular and '''Old Wide'''.
:*'''''Ambient Light Level''''' is a slider that adjusts the visibility of the game. Depending on the selected screen resolution is affects the visibility of the scene and objects within.

==OpenGL==

===Texture Filter===
:'''''Texture Filter''''' blurs highres textures to "smooth over" visible pixels. Six filter types are available, '''Nearest''' (basic), '''Nearest-MM-Nearest''', '''Nearest-MM-Linear''', '''Linear''', '''Bilinear''' and '''Trilinear'''. For the original 8-bit art, '''Nearest-MM-Linear''' is highly recommended. For highres art, '''Trilinear''' is recommended.

===Renderer Setup===
:'''''Renderer Setup''''' opens to the the following sub-menu when in the OpenGL mode:
:*'''''Aspect Ratio''''' is an adjustment for the selected screen resolution. '''Auto''' is recommended for most systems. In the OpenGL mode, the available ratios of 1.33:1, 1.66:1, 1.78:1, 1.85:1 or 2.35:1 can be selected with the arrow keys.
:*'''''Ambient Light Level''''' adjusts the illumination of the game with a slider. Depending on the selected screen resolution, it affects the visibility of the scene and objects within.
:*'''''Anisotropic Filtering''''' means filter (sharpen) distant scenes viewed from an angle. What is available is '''2x''' (2:1), '''4x''' (4:1), '''8x''' (8:1), '''16x''' (16:1) and '''None'''. Consult the specification of your video card for the highest setting you can (should) use.
:*'''''Use VSync''''' avoids tearing the screens. It should only be set to '''No''' if your video card cannot handle the resulting processor load.
:*'''''Enable Highres Textures''''' utilizes any defined [[DEF Language#texture|hightile textures]] and enables the other related options:
::* '''''Highres Texture Quality''''' is slider for fine tune the sharpness of the textures.
::* '''''Preload Map Textures''''' is a toggle to either preload the textures ('''On''') before playing the map or loading them during play ('''Off''').
::* '''''Use Texture Cache''''' can be enabled with '''On''' or '''Compressed'''. This currently works only for NVIDIA graphics cards. AMD users should leave this to '''Off'''.
::*'''''Use Detailed Textures''''' is an option to enable any defined [[detail mapping|detail maps]].
*'''''Use Models''''' is a toggle to utilize any defined [[DEF Language#model|3D models]].

[[Category:EDuke32 end-user documentation]]

Talk:Video setup

2012-05-08T00:14:49Z

Hank:

I am planing to describe basic video setup 'software' and 'OpenGL' on that page. I guess this page was deleted for vandalism only. If I am wrong and it should be kept blank for now, let me know. :)
best [[User:Hank|Hank]] ([[User talk:Hank|talk]]) 10:47, 6 May 2012 (PDT)
:Thanks for filling this in! -[[User:Hendricks 266|Hendricks266]] ([[User talk:Hendricks 266|talk]]) 13:11, 6 May 2012 (PDT)
Any time - I added the rest for OpenGL. Needs checking also, and we should be done for while.
Cheers - [[User:Hank|Hank]] ([[User talk:Hank|talk]]) 15:35, 6 May 2012 (PDT)

Corrected my grammar. :( - Cheers [[User:Hank|Hank]] ([[User talk:Hank|talk]]) 17:14, 7 May 2012 (PDT)

Video setup

2012-05-08T00:12:49Z

Hank: /* Renderer Setup */

The '''''video setup''''' menu is used to adjust several aspects of the game's video display.

==Common Settings==

===Resolution===
:'''''Resolution''''' allows you to select the screen resolution. Use the arrow keys to dial through all available screen resolutions.

===Renderer===
:'''''Renderer''''' allows two render options, Software or OpenGL. There are in fact three [[rendmode|renderers]] in the game which can be toggled with the [[console commands#setrendermode|setrendermode console command]].

===Full Screen===
:'''''Full Screen''''' is a toggle for '''Yes''' (Full Screen) or '''No''' (Windowed).

===Color Correction===
:'''''Color Correction''''' opens to the the following sub-menu:
:*'''''Gamma''''' is a slider to adjust the [[Wikipedia:Gamma_correction|gamma]] of the display.
:*'''''Contrast''''' is a slider to adjust the [[Wikipedia:Contrast_(Vision)|contrast]] of the display.
:*'''''Brightness''''' is a slider to adjust [[Wikipedia:Luma_(video)|brightness]] of the display.

==Software==

===Pixel Doubling===
:'''''Pixel Doubling''''' is the correct terminology for the '''''Detail''''' option in the original game's option menu, with '''Off''' corresponding to High Detail and '''On''' to Low Detail. When enabled, this setting cuts the amount of detail on screen in half by drawing the game viewport at half the current resolution then doubling the pixels from 1x1 to 2x2. This option only appears for the Classic renderer and is recommended to be '''Off''' at all times unless the hardware you are using is incredibly weak making this a necessity.

===Renderer Setup===
:'''''Renderer Setup''''' when in the 'Software' mode opens to the the following sub-menu:
:*'''''Aspect Ratio''''' is an adjustment for the selected screen resolution. '''Auto''' is recommended for most systems. Other options are '''Old Reg'''ular and '''Old Wide'''.
:*'''''Ambient Light Level''''' is a slider that adjusts the visibility of the game. Depending on the selected screen resolution is affects the visibility of the scene and objects within.

==OpenGL==

===Texture Filter===
:'''''Texture Filter''''' blurs highres textures to "smooth over" visible pixels. Six filter types are available, '''Nearest''' (basic), '''Nearest-MM-Nearest''', '''Nearest-MM-Linear''', '''Linear''', '''Bilinear''' and '''Trilinear'''. For the original 8-bit art, '''Nearest-MM-Linear''' is highly recommended. For highres art, '''Trilinear''' is recommended.

===Renderer Setup===
:'''''Renderer Setup''''' opens to the the following sub-menu when in the OpenGL mode:
:*'''''Aspect Ratio''''' is an adjustment for the selected screen resolution. '''Auto''' is recommended for most systems. In the OpenGL mode, the available ratios of 1.33:1, 1.66:1, 1.78:1, 1.85:1 or 2.35:1 can be selected with the arrow keys.
:*'''''Ambient Light Level''''' adjusts the illumination of the game with a slider. Depending on the selected screen resolution it affects the visibility of the scene and objects within.
:*'''''Anisotropic Filtering''''' means filter (sharpen) distant scenes viewed from an angle. What is available is '''2x''' (2:1), '''4x''' (4:1), '''8x''' (8:1), '''16x''' (16:1) and '''None'''. Consult the specification of your video card for the highest setting you can (should) use.
:*'''''Use VSync''''' avoids tearing the screens. It should only be set to '''No''' if your video card cannot handle the resulting processor load.
:*'''''Enable Highres Textures''''' utilizes any defined [[DEF Language#texture|hightile textures]] and enables the other related options:
::* '''''Highres Texture Quality''''' is slider for fine tune the sharpness of the textures.
::* '''''Preload Map Textures''''' is a toggle to either preload the textures ('''On''') before playing the map or loading them during play ('''Off''').
::* '''''Use Texture Cache''''' can be enabled with '''On''' or '''Compressed'''. This currently works only for NVIDIA graphics cards. AMD users should leave this to '''Off'''.
::*'''''Use Detailed Textures''''' is an option to enable any defined [[detail mapping|detail maps]].
*'''''Use Models''''' is a toggle to utilize any defined [[DEF Language#model|3D models]].

[[Category:EDuke32 end-user documentation]]

Video setup

2012-05-07T00:40:34Z

Hank: /* Renderer Setup – OpenGL */

Video setup

2012-05-06T22:37:47Z

Hank: /* Renderer Setup – OpenGL */

Talk:Video setup

2012-05-06T22:35:13Z

Hank:

Video setup

2012-05-06T22:32:57Z

Hank:

Video setup

2012-05-06T19:14:52Z

Hank: Created page with "The '''''video' setup''''' menu is used to adjust several aspects of the game's video display. ===Resolution=== :'''''Resolution''''' allows you to select the screen resoluti..."

Talk:Video setup

2012-05-06T17:47:57Z

Hank: Created page with "I am planing to describe basic video setup 'software' and 'OpenGL' on that page. I guess this page was deleted for vandalism only. If I am wrong and it should be kept blank fo..."

Category:Editing Moving Sectors

2012-05-05T06:55:30Z

Hank: /* Automated Two-Way Trains */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Rotating Sectors (Gears)==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-H)''

This effect allows you to create a constantly rotating sector, such as the gears found in the registered levels.

:STEP 1: Create the sector to be rotated.

:STEP 2: Place one sector effector sprite where you want the pivot point for this sector to be (it is usually placed in the center). Give this sprite a lotag value of 1, and a unique hitag value. This hitag must be greater than zero. Now change the angle of this sprite to one of the following: 
:'''Up''' - Sector rotates counter-clockwise 
:'''Down''' - Sector rotates clockwise

:::''NOTE 1:'' This pivot point sprite is not required to be inside the sector that will rotate.

:STEP 3: Place one other sector effector sprite somewhere else in your gear sector. Give this sprite the same unique hitag value that you gave the first sector effector sprite. Leave the lotag value set as 0. Then set the angle of this sector effector sprite. The following angles have the following related functions: 
:'''Up''' - All points of sector rotate around pivot point 
:'''Down''' - Entire sector rotates around pivot point

:STEP 4: If you want sprites and the player to rotate with this sector, you must enter 3D mode and press the [R] key on the floor of the sector. This will allow sprites and actors to move with the rotating sector.

==Using Rotating Sectors for Doors==

''Map Name: [[Media:Rotatedr.map|ROTATEDR.MAP]]''

Rotating sectors can be used in combination with switches to create a very interesting type of door. The how-to is fairly complicated, so a tutorial map (created by Jack Gutzler AKA Captain Massive) has been included with this package.

==Two-Way Trains==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-D)''

Two-way trains are very cool and a great addition to any level. They are, however, quite complex to build.

:STEP 1: Create the track for the train (it should be straight), the train itself, and two rooms at either end of the track.

:::''NOTE 1:'' The train sector should not be split into multiple sectors. However, the train can include white-walled (non-valid player space) sectors and nested red-lined sectors (take a look at the tutorial map to see exactly what is possible).

:::''NOTE 2:'' The train should be made on the opposite side of the track from which the player will enter first. And the train should not be made right in front of where the player will board it (place the train in the middle of the track for now).

:STEP 2: Place three switches on the map: one in the train, and the other two in both rooms at either end of the track (i.e. - one in each room).

:STEP 3: Give all three switch sprites the same, unique lotag value.

:STEP 4: Place one activator sprite in the train and give it the same lotag value that you gave the switch sprites.

:STEP 5: Place one sector effector sprite in the train and give it a lotag value of 30. Give this sprite a hitag value of 1 added to the value you gave the switch sprites (so if your switch sprite lotag was 10, the hitag value of this sector effector sprite would be 11). You now must change the angle value for this sprite. Point it in the direction of the track where the train will start from (if your train starts from the left hand side, point the sector effector sprite to the left).

:STEP 6: Give the train sector a sector lotag value of 31.

:STEP 7: Place two locator sprites (sprite #6) on your track, one where the train will begin and one where the train will stop. Think of these two sprites as reference sprites. The sector effector sprite that you placed in your train sector is a fixed point on your train. When the train moves from point to point, the fixed sector effector on the train will move over top of the locator sprites. So place these in an appropriate place. Give the locator closest to where the player will first board the train a lotag value of 1 and a hitag value of 1. Do not give the other locator sprite a lotag or hitag value (both should remain at the default value of 0).

:STEP 8: In 3D mode, press the [R] key on the floor of your train. If your train has a ceiling, do the same thing.

===Optional Steps===

:STEP 9: Create door sectors on each end of the track where the player will board and exit the train. They should be regular Doom-type doors. Place one activator sprite in each door sector. Give the activator sprite in the door where the player will first board the train, a lotag value of two more than the switch lotag. For example, if the switch lotag (near the door) was 10, the lotag of this activator sprite would be 12.

:STEP 10: Give the other activator sprite (in the other door sector) a lotag value of one more than the switch sprite lotag. For example, if the switch lotag was 10, the lotag of this second activator sprite would be 11.

:STEP 11: Make sure that the door where the player will first board the train is in the closed position. The other door (at the other end of the track) should be open. If this is not set properly, the timing of the doors will be off.

==Automated Two-Way Trains==

''Map Name: [[Media:Autotrain.map|Autotrain.map]]''

Originally developed by Paul B.

If the train should operate automatically, follow the Two-Way Trains setup with the following exceptions:
*1. Omit any switches and give the Activator Sprite a unique lotag; and set the hitag of SE30 to the unique lotag+1)
*2. Place another Sector Effector Sprite in the train section, and give it a lotag of 10.
*3. Set the hitag of this SE sprite to how long it should take for the train to hold before travelling in one or the other direction.

: Note: The Sector Effector 'Door Auto Close' (SE10) works as a trigger for Two-Way Trains (S31).

==One Car Subways==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-E)''

Subways are not difficult to master, but they do require patience and a great deal of work. But they can be done, and they can be a great addition to any level!

:STEP 1: Make the track for the subway. For this example we will be making a simple rectangle room. Later on, when you get practice with the Locator sprites, you will be able to have a track with a more realistic look (i.e. - Walls on both sides of the track. Here we are just using an open room which the subway will wander around in). Set your textures to whatever you want.

:STEP 2: Make a sector off of this room (or anywhere else for that matter) to be a station for the train. Make sure the sector is valid player space, and raise it up from the floor of the track sector in 3D mode (this sector will be higher up than the track).

:STEP 3: Make one other rectangular sector that will be the subway car itself. Do not make the car right next to the station, as a locator sprite will be needed for that. Raise the car up out of the ground, and make it valid player space. Choose appropriate textures.

:STEP 4: In 2D mode, put the mouse cursor in the subway car sector and press the [H] key. You now will give that sector a hitag of 1. This number is an indicator for the cars, so if you had a second subway somewhere else on your map, the cars would have a hitag of 2.

:STEP 5: Now insert a sprite in the subway car sector by pressing [S] in 2D mode. Now go into 3D mode and press [V] on the newly made sprite twice. Change the sprite into a sector-effector sprite. Place the sprite in the center of the car and change the angle of the sprite to be in the direction of the front of the car. The sprite's angle tells the subway in which direction it will go. Press [R] on the floor of the subway (and on the ceiling too if your subway has a ceiling. If it does not have a ceiling, leave it alone) in 3D mode. This makes the floor move with the train.

:STEP 6: Go into 2D mode and press [ALT]+[T] on the sprite, and enter the value of 6. This gives the sector-effector sprite a lotag of 6 and it makes this car the "engine" of the subway. When you make a multiple car subway, this will be the lead car of the subway. It will pull all of the other cars behind it.

:STEP 7: Now you must place the locator sprites all over the track. These sprites make the actual 'path' of the train. Place a locator sprite near the station and give it a hitag of 1, and leave the lotag at 0. The hitag of 1 tells the subway that it must stop at this point of the track and wait for five seconds.

:STEP 8: Now put Locator sprites all around the track. Put the sprites anywhere in your track that you want your train to go. The train will go over all the Locator sprites you put down, so place them in the way you want your train to go.

:STEP 9: You now must give the Locator sprites lotags that go in numeric order. For example, the Locator that the train will go to, AFTER visiting the station would have a lotag of 1. The next sprite will have a lotag of 2, the next a lotag of 3, and so on. This will continue until you get back to the station locator (the one with the hitag of 1). DO NOT GIVE THE STATION LOCATOR A LOTAG! IT MUST BE LEFT AT 0! Make sure that you make the track for the subway as accurate as possible, as the subway can sometimes disappear. You are all done at this point!

==Making Multi-Car Subways==

''Map Name: NONE''

Multi car subways are just as easy as one car subways, but it requires some work and time.

:STEP 1: Make the first car, or "engine" of the train by following the instructions in the above how-to.

:STEP 2: Make several more car sectors behind the engine of the train, make them valid player space, and choose appropriate textures for the car. The train cars should *not* be connected, and there should be some space between the two. When the train turns around a corner, sometimes the train sectors can overlap, causing some strange bugs to appear. So don't put them too close. Also make sure that the cars are raised out of the ground to the appropriate height (whatever you want it to be).

:STEP 3: Give the car sectors a hitag of 1 (not necessary, but it is if you have more than one subway on your map. If you had a second subway, the cars hitag would be 2, and so on).

:STEP 4: Put a sector effector sprite in the cars of the train and give them a lotag of 14, which means that these cars will follow the "engine" of the train.

:STEP 5: You're done (the path for the train should have already been made, as you constructed that in the first how-to).

==Notes on Subways==

''Map Name: NONE''

Here is a short list of notes that might make your subway making problems disappear. Many problems can be solved with some of these notes, so read on!

:1. The locators should _all_ be in the same sector (the track). It is not advised to split up the track sector, but if you must do it make sure the locators are all in the same sector.

:2. The pixel height (height between floor and ceiling) of the train has to have a maximum of 104 in order to run you over. If the pixel height is more than this the train will pass through you instead of killing you (weird, eh?).

:3. A train with cars behind it will travel slightly faster than a single train! So be aware that when you put 2 trains on the same track, after quite a while, they will have caught up with each other (I actually did this).

==Rotating & Rising Sectors==

This is covered in the section [[:Category:Editing_Sectors_That_Rise_and_Fall#Rotating & Rising Sectors]].

Category:Editing Moving Sectors

2012-05-05T05:25:29Z

Hank: /* Automated Two-Way Trains */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Rotating Sectors (Gears)==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-H)''

This effect allows you to create a constantly rotating sector, such as the gears found in the registered levels.

:STEP 1: Create the sector to be rotated.

:STEP 2: Place one sector effector sprite where you want the pivot point for this sector to be (it is usually placed in the center). Give this sprite a lotag value of 1, and a unique hitag value. This hitag must be greater than zero. Now change the angle of this sprite to one of the following: 
:'''Up''' - Sector rotates counter-clockwise 
:'''Down''' - Sector rotates clockwise

:::''NOTE 1:'' This pivot point sprite is not required to be inside the sector that will rotate.

:STEP 3: Place one other sector effector sprite somewhere else in your gear sector. Give this sprite the same unique hitag value that you gave the first sector effector sprite. Leave the lotag value set as 0. Then set the angle of this sector effector sprite. The following angles have the following related functions: 
:'''Up''' - All points of sector rotate around pivot point 
:'''Down''' - Entire sector rotates around pivot point

:STEP 4: If you want sprites and the player to rotate with this sector, you must enter 3D mode and press the [R] key on the floor of the sector. This will allow sprites and actors to move with the rotating sector.

==Using Rotating Sectors for Doors==

''Map Name: [[Media:Rotatedr.map|ROTATEDR.MAP]]''

Rotating sectors can be used in combination with switches to create a very interesting type of door. The how-to is fairly complicated, so a tutorial map (created by Jack Gutzler AKA Captain Massive) has been included with this package.

==Two-Way Trains==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-D)''

Two-way trains are very cool and a great addition to any level. They are, however, quite complex to build.

:STEP 1: Create the track for the train (it should be straight), the train itself, and two rooms at either end of the track.

:::''NOTE 1:'' The train sector should not be split into multiple sectors. However, the train can include white-walled (non-valid player space) sectors and nested red-lined sectors (take a look at the tutorial map to see exactly what is possible).

:::''NOTE 2:'' The train should be made on the opposite side of the track from which the player will enter first. And the train should not be made right in front of where the player will board it (place the train in the middle of the track for now).

:STEP 2: Place three switches on the map: one in the train, and the other two in both rooms at either end of the track (i.e. - one in each room).

:STEP 3: Give all three switch sprites the same, unique lotag value.

:STEP 4: Place one activator sprite in the train and give it the same lotag value that you gave the switch sprites.

:STEP 5: Place one sector effector sprite in the train and give it a lotag value of 30. Give this sprite a hitag value of 1 added to the value you gave the switch sprites (so if your switch sprite lotag was 10, the hitag value of this sector effector sprite would be 11). You now must change the angle value for this sprite. Point it in the direction of the track where the train will start from (if your train starts from the left hand side, point the sector effector sprite to the left).

:STEP 6: Give the train sector a sector lotag value of 31.

:STEP 7: Place two locator sprites (sprite #6) on your track, one where the train will begin and one where the train will stop. Think of these two sprites as reference sprites. The sector effector sprite that you placed in your train sector is a fixed point on your train. When the train moves from point to point, the fixed sector effector on the train will move over top of the locator sprites. So place these in an appropriate place. Give the locator closest to where the player will first board the train a lotag value of 1 and a hitag value of 1. Do not give the other locator sprite a lotag or hitag value (both should remain at the default value of 0).

:STEP 8: In 3D mode, press the [R] key on the floor of your train. If your train has a ceiling, do the same thing.

===Optional Steps===

:STEP 9: Create door sectors on each end of the track where the player will board and exit the train. They should be regular Doom-type doors. Place one activator sprite in each door sector. Give the activator sprite in the door where the player will first board the train, a lotag value of two more than the switch lotag. For example, if the switch lotag (near the door) was 10, the lotag of this activator sprite would be 12.

:STEP 10: Give the other activator sprite (in the other door sector) a lotag value of one more than the switch sprite lotag. For example, if the switch lotag was 10, the lotag of this second activator sprite would be 11.

:STEP 11: Make sure that the door where the player will first board the train is in the closed position. The other door (at the other end of the track) should be open. If this is not set properly, the timing of the doors will be off.

==Automated Two-Way Trains==

''Map Name: [[Media:Autotrain.map|Autotrain.map]]''

Originally developed by Paul B.

If the train should operate automatically, follow the Two-Way Trains setup with the following exceptions:
*1. Omit any switches and give the Activator Sprite a unique lotag.
*2. Place another Sector Effector Sprite in the train section, and give it a lotag of 10.
*3. Set the hitag of this SE sprite to how long it should take for the train to hold before travelling in one or the other direction.

: Note: The Sector Effector 'Door Auto Close' (SE10) works as a trigger for Two-Way Trains (S31).

==One Car Subways==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-E)''

Subways are not difficult to master, but they do require patience and a great deal of work. But they can be done, and they can be a great addition to any level!

:STEP 1: Make the track for the subway. For this example we will be making a simple rectangle room. Later on, when you get practice with the Locator sprites, you will be able to have a track with a more realistic look (i.e. - Walls on both sides of the track. Here we are just using an open room which the subway will wander around in). Set your textures to whatever you want.

:STEP 2: Make a sector off of this room (or anywhere else for that matter) to be a station for the train. Make sure the sector is valid player space, and raise it up from the floor of the track sector in 3D mode (this sector will be higher up than the track).

:STEP 3: Make one other rectangular sector that will be the subway car itself. Do not make the car right next to the station, as a locator sprite will be needed for that. Raise the car up out of the ground, and make it valid player space. Choose appropriate textures.

:STEP 4: In 2D mode, put the mouse cursor in the subway car sector and press the [H] key. You now will give that sector a hitag of 1. This number is an indicator for the cars, so if you had a second subway somewhere else on your map, the cars would have a hitag of 2.

:STEP 5: Now insert a sprite in the subway car sector by pressing [S] in 2D mode. Now go into 3D mode and press [V] on the newly made sprite twice. Change the sprite into a sector-effector sprite. Place the sprite in the center of the car and change the angle of the sprite to be in the direction of the front of the car. The sprite's angle tells the subway in which direction it will go. Press [R] on the floor of the subway (and on the ceiling too if your subway has a ceiling. If it does not have a ceiling, leave it alone) in 3D mode. This makes the floor move with the train.

:STEP 6: Go into 2D mode and press [ALT]+[T] on the sprite, and enter the value of 6. This gives the sector-effector sprite a lotag of 6 and it makes this car the "engine" of the subway. When you make a multiple car subway, this will be the lead car of the subway. It will pull all of the other cars behind it.

:STEP 7: Now you must place the locator sprites all over the track. These sprites make the actual 'path' of the train. Place a locator sprite near the station and give it a hitag of 1, and leave the lotag at 0. The hitag of 1 tells the subway that it must stop at this point of the track and wait for five seconds.

:STEP 8: Now put Locator sprites all around the track. Put the sprites anywhere in your track that you want your train to go. The train will go over all the Locator sprites you put down, so place them in the way you want your train to go.

:STEP 9: You now must give the Locator sprites lotags that go in numeric order. For example, the Locator that the train will go to, AFTER visiting the station would have a lotag of 1. The next sprite will have a lotag of 2, the next a lotag of 3, and so on. This will continue until you get back to the station locator (the one with the hitag of 1). DO NOT GIVE THE STATION LOCATOR A LOTAG! IT MUST BE LEFT AT 0! Make sure that you make the track for the subway as accurate as possible, as the subway can sometimes disappear. You are all done at this point!

==Making Multi-Car Subways==

''Map Name: NONE''

Multi car subways are just as easy as one car subways, but it requires some work and time.

:STEP 1: Make the first car, or "engine" of the train by following the instructions in the above how-to.

:STEP 2: Make several more car sectors behind the engine of the train, make them valid player space, and choose appropriate textures for the car. The train cars should *not* be connected, and there should be some space between the two. When the train turns around a corner, sometimes the train sectors can overlap, causing some strange bugs to appear. So don't put them too close. Also make sure that the cars are raised out of the ground to the appropriate height (whatever you want it to be).

:STEP 3: Give the car sectors a hitag of 1 (not necessary, but it is if you have more than one subway on your map. If you had a second subway, the cars hitag would be 2, and so on).

:STEP 4: Put a sector effector sprite in the cars of the train and give them a lotag of 14, which means that these cars will follow the "engine" of the train.

:STEP 5: You're done (the path for the train should have already been made, as you constructed that in the first how-to).

==Notes on Subways==

''Map Name: NONE''

Here is a short list of notes that might make your subway making problems disappear. Many problems can be solved with some of these notes, so read on!

:1. The locators should _all_ be in the same sector (the track). It is not advised to split up the track sector, but if you must do it make sure the locators are all in the same sector.

:2. The pixel height (height between floor and ceiling) of the train has to have a maximum of 104 in order to run you over. If the pixel height is more than this the train will pass through you instead of killing you (weird, eh?).

:3. A train with cars behind it will travel slightly faster than a single train! So be aware that when you put 2 trains on the same track, after quite a while, they will have caught up with each other (I actually did this).

==Rotating & Rising Sectors==

This is covered in the section [[:Category:Editing_Sectors_That_Rise_and_Fall#Rotating & Rising Sectors]].

Category:Editing Moving Sectors

2012-05-05T03:18:19Z

Hank:

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Rotating Sectors (Gears)==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-H)''

This effect allows you to create a constantly rotating sector, such as the gears found in the registered levels.

:STEP 1: Create the sector to be rotated.

:STEP 2: Place one sector effector sprite where you want the pivot point for this sector to be (it is usually placed in the center). Give this sprite a lotag value of 1, and a unique hitag value. This hitag must be greater than zero. Now change the angle of this sprite to one of the following: 
:'''Up''' - Sector rotates counter-clockwise 
:'''Down''' - Sector rotates clockwise

:::''NOTE 1:'' This pivot point sprite is not required to be inside the sector that will rotate.

:STEP 3: Place one other sector effector sprite somewhere else in your gear sector. Give this sprite the same unique hitag value that you gave the first sector effector sprite. Leave the lotag value set as 0. Then set the angle of this sector effector sprite. The following angles have the following related functions: 
:'''Up''' - All points of sector rotate around pivot point 
:'''Down''' - Entire sector rotates around pivot point

:STEP 4: If you want sprites and the player to rotate with this sector, you must enter 3D mode and press the [R] key on the floor of the sector. This will allow sprites and actors to move with the rotating sector.

==Using Rotating Sectors for Doors==

''Map Name: [[Media:Rotatedr.map|ROTATEDR.MAP]]''

Rotating sectors can be used in combination with switches to create a very interesting type of door. The how-to is fairly complicated, so a tutorial map (created by Jack Gutzler AKA Captain Massive) has been included with this package.

==Two-Way Trains==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-D)''

Two-way trains are very cool and a great addition to any level. They are, however, quite complex to build.

:STEP 1: Create the track for the train (it should be straight), the train itself, and two rooms at either end of the track.

:::''NOTE 1:'' The train sector should not be split into multiple sectors. However, the train can include white-walled (non-valid player space) sectors and nested red-lined sectors (take a look at the tutorial map to see exactly what is possible).

:::''NOTE 2:'' The train should be made on the opposite side of the track from which the player will enter first. And the train should not be made right in front of where the player will board it (place the train in the middle of the track for now).

:STEP 2: Place three switches on the map: one in the train, and the other two in both rooms at either end of the track (i.e. - one in each room).

:STEP 3: Give all three switch sprites the same, unique lotag value.

:STEP 4: Place one activator sprite in the train and give it the same lotag value that you gave the switch sprites.

:STEP 5: Place one sector effector sprite in the train and give it a lotag value of 30. Give this sprite a hitag value of 1 added to the value you gave the switch sprites (so if your switch sprite lotag was 10, the hitag value of this sector effector sprite would be 11). You now must change the angle value for this sprite. Point it in the direction of the track where the train will start from (if your train starts from the left hand side, point the sector effector sprite to the left).

:STEP 6: Give the train sector a sector lotag value of 31.

:STEP 7: Place two locator sprites (sprite #6) on your track, one where the train will begin and one where the train will stop. Think of these two sprites as reference sprites. The sector effector sprite that you placed in your train sector is a fixed point on your train. When the train moves from point to point, the fixed sector effector on the train will move over top of the locator sprites. So place these in an appropriate place. Give the locator closest to where the player will first board the train a lotag value of 1 and a hitag value of 1. Do not give the other locator sprite a lotag or hitag value (both should remain at the default value of 0).

:STEP 8: In 3D mode, press the [R] key on the floor of your train. If your train has a ceiling, do the same thing.

===Optional Steps===

:STEP 9: Create door sectors on each end of the track where the player will board and exit the train. They should be regular Doom-type doors. Place one activator sprite in each door sector. Give the activator sprite in the door where the player will first board the train, a lotag value of two more than the switch lotag. For example, if the switch lotag (near the door) was 10, the lotag of this activator sprite would be 12.

:STEP 10: Give the other activator sprite (in the other door sector) a lotag value of one more than the switch sprite lotag. For example, if the switch lotag was 10, the lotag of this second activator sprite would be 11.

:STEP 11: Make sure that the door where the player will first board the train is in the closed position. The other door (at the other end of the track) should be open. If this is not set properly, the timing of the doors will be off.

==Automated Two-Way Trains==

''Map Name: [[Media:Autotrain.map|Autotrain.map]]''

Originally developed by Paul B.

If the train should operate automatically, follow the Two-Way Trains setup with the following exceptions:
*1. Omit any switches and give the Activator Sprite a unique lotag.
*2. Place another Sector Effector Sprite in the train section, and give it a lowtag of 10.
*3. Set the hitag of this SE sprite to how long it should take for the train to hold before travelling in one or the other direction.

: Note: The Sector Effector 'Door Auto Close' (SE10) works as a trigger for Two-Way Trains (S31).

==One Car Subways==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-E)''

Subways are not difficult to master, but they do require patience and a great deal of work. But they can be done, and they can be a great addition to any level!

:STEP 1: Make the track for the subway. For this example we will be making a simple rectangle room. Later on, when you get practice with the Locator sprites, you will be able to have a track with a more realistic look (i.e. - Walls on both sides of the track. Here we are just using an open room which the subway will wander around in). Set your textures to whatever you want.

:STEP 2: Make a sector off of this room (or anywhere else for that matter) to be a station for the train. Make sure the sector is valid player space, and raise it up from the floor of the track sector in 3D mode (this sector will be higher up than the track).

:STEP 3: Make one other rectangular sector that will be the subway car itself. Do not make the car right next to the station, as a locator sprite will be needed for that. Raise the car up out of the ground, and make it valid player space. Choose appropriate textures.

:STEP 4: In 2D mode, put the mouse cursor in the subway car sector and press the [H] key. You now will give that sector a hitag of 1. This number is an indicator for the cars, so if you had a second subway somewhere else on your map, the cars would have a hitag of 2.

:STEP 5: Now insert a sprite in the subway car sector by pressing [S] in 2D mode. Now go into 3D mode and press [V] on the newly made sprite twice. Change the sprite into a sector-effector sprite. Place the sprite in the center of the car and change the angle of the sprite to be in the direction of the front of the car. The sprite's angle tells the subway in which direction it will go. Press [R] on the floor of the subway (and on the ceiling too if your subway has a ceiling. If it does not have a ceiling, leave it alone) in 3D mode. This makes the floor move with the train.

:STEP 6: Go into 2D mode and press [ALT]+[T] on the sprite, and enter the value of 6. This gives the sector-effector sprite a lotag of 6 and it makes this car the "engine" of the subway. When you make a multiple car subway, this will be the lead car of the subway. It will pull all of the other cars behind it.

:STEP 7: Now you must place the locator sprites all over the track. These sprites make the actual 'path' of the train. Place a locator sprite near the station and give it a hitag of 1, and leave the lotag at 0. The hitag of 1 tells the subway that it must stop at this point of the track and wait for five seconds.

:STEP 8: Now put Locator sprites all around the track. Put the sprites anywhere in your track that you want your train to go. The train will go over all the Locator sprites you put down, so place them in the way you want your train to go.

:STEP 9: You now must give the Locator sprites lotags that go in numeric order. For example, the Locator that the train will go to, AFTER visiting the station would have a lotag of 1. The next sprite will have a lotag of 2, the next a lotag of 3, and so on. This will continue until you get back to the station locator (the one with the hitag of 1). DO NOT GIVE THE STATION LOCATOR A LOTAG! IT MUST BE LEFT AT 0! Make sure that you make the track for the subway as accurate as possible, as the subway can sometimes disappear. You are all done at this point!

==Making Multi-Car Subways==

''Map Name: NONE''

Multi car subways are just as easy as one car subways, but it requires some work and time.

:STEP 1: Make the first car, or "engine" of the train by following the instructions in the above how-to.

:STEP 2: Make several more car sectors behind the engine of the train, make them valid player space, and choose appropriate textures for the car. The train cars should *not* be connected, and there should be some space between the two. When the train turns around a corner, sometimes the train sectors can overlap, causing some strange bugs to appear. So don't put them too close. Also make sure that the cars are raised out of the ground to the appropriate height (whatever you want it to be).

:STEP 3: Give the car sectors a hitag of 1 (not necessary, but it is if you have more than one subway on your map. If you had a second subway, the cars hitag would be 2, and so on).

:STEP 4: Put a sector effector sprite in the cars of the train and give them a lotag of 14, which means that these cars will follow the "engine" of the train.

:STEP 5: You're done (the path for the train should have already been made, as you constructed that in the first how-to).

==Notes on Subways==

''Map Name: NONE''

Here is a short list of notes that might make your subway making problems disappear. Many problems can be solved with some of these notes, so read on!

:1. The locators should _all_ be in the same sector (the track). It is not advised to split up the track sector, but if you must do it make sure the locators are all in the same sector.

:2. The pixel height (height between floor and ceiling) of the train has to have a maximum of 104 in order to run you over. If the pixel height is more than this the train will pass through you instead of killing you (weird, eh?).

:3. A train with cars behind it will travel slightly faster than a single train! So be aware that when you put 2 trains on the same track, after quite a while, they will have caught up with each other (I actually did this).

==Rotating & Rising Sectors==

This is covered in the section [[:Category:Editing_Sectors_That_Rise_and_Fall#Rotating & Rising Sectors]].

File:Autotrain.map

2012-05-05T02:57:00Z

Hank: A simple map showing an automated 2-Way train

A simple map showing an automated 2-Way train

Category:Editing Ending the Level

2012-05-01T01:16:10Z

Hank: /* Switch Operated End of Level Sector */

Category:Editing Switch Effects

2012-05-01T00:48:17Z

Hank: /* Multi-Door Switches */

Door Sounds

2012-04-23T20:28:36Z

Hank: /* Adding Sounds to Doors */

Door Sounds

2012-04-23T20:25:13Z

Hank: /* Adding Sounds to Doors */

Definesound

2012-04-22T18:32:40Z

Hank:

'''definesound''' <value> <filename> <pitch1> <pitch2> <priority> <type> <volume>

The definesound command defines a sound and assigns various properties to it. The maximum number of sounds that can be defined is 4096 for EDuke32, and 450 for Duke v1.5.
*<value>: This can be either the sound's number or the name that has been [[define]]d for that number.
*<filename>: The name of the sound file. Sound files are assumed to be in the same directory as the program unless a folder path is specified. Assume that the user's OS is case sensitive, and directory delimiters are forward slashes (<code>/</code>) rather than backslashes (<code>\</code>).
*<pitch1> and <pitch2>: These are a random pitch variation range. Values may be positive or negative. For example, if you want you sound to have a chance of both moderate increase and decrease in pitch, you would use values such as <code>-512 512</code>.
*<priority>: A value of 0 to 255 indicates the priority the sound has over other sounds that are playing simultaneously. The higher the value, the greater its priority. This is due to the limit on the number of sounds that can play at once. Take a look at the original USER.CON to see what kinds of sounds get what kinds of priority. For example, most Duke remarks are maxed out at 255.
*<type>: This flag is a [[bitfield]] which indicates what type of sound you are defining.
:Bit #0 ('''1'''): The sound repeats if continually played.
:Bit #1 ('''2'''): The sound is an ambient effect. Disabling ambience in the menu will mute this sound.
::Bit #0 + Bit #1 ('''3'''): The sound will loop until instructed to stop.
:Bit #2 ('''4'''): The sound is a player voice. Disabling "Duke Talk" in the menu will mute this sound.
:Bit #3 ('''8'''): The sound contains offensive content. Disabling "Adult Mode" or enabling the parental lock in the menu will mute this sound.
:Bit #4 ('''16'''): The sound will always be heard from anywhere in the level. (See [[globalsound]].) (sndist = 0)
:Bit #7 ('''128'''): The sound is used in Duke-Tag.
*<volume>: Negative values increase volume; positive ones soften it. Can range from -32768 to 32767. Note that this value does not actually affect the sound's volume, but rather it modifies the distance registered between it and any listening players. As such, this has no effect on global sounds or sounds made by the player.

[[Category:Duke3D 1.3/1.5 commands]]
[[Category:Sound manipulation]]

Sliding Doors

2012-04-20T02:11:23Z

Hank: /* Alternate See-Through Sliding Doors */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.

==Sliding Doors==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-C)''

Again, due to the extremely difficult task of explaining this how-to, I have provided a step by step example in the tutorial map, showing how to make this door. Just take a look at the example and it should make sense (it goes step by step in the building process).

==Alternate Sliding Doors==
''Map Name: [[Media:Altslidoor.map|Altslidoor.map]] (Room 1)''

The concept was originally posted by Ursurper in the Dukeworld forum, a very long time ago. It works for Mapster32, is efficient to make and very simple.

*Step 1: Make a sector that will be your entire door sector. It needs to be long enough to hold the sliding door itself and when the door is in the open position. Split (mark) this sector in two if two sliding doors are to operate.
*Step 2: Create one child sector in the sector of step one, this will be the door itself.
*Step 3: Give each door sector a lotag of 25, and an SE sprite with a lowtag of 15 and a unique hitag. Point the tail of the SE to the same direction as the door will move when it closes.
*Step 4: Add a [[GPSPEED]] to this sector and set the the lotag to the distance the door is to travel.
*Step 5: Add a [[Music&SFX]] Sprite and if required, [[Activator]]s and switches to control the door.

Note 1: If you want to use a switch that opens two sliding doors (as in a elevator), place two [[Activator]] sprites in one door sector, and one in the other. Give all three [[Activator]]s the same unique lotag as the switch.

==See Through Sliding Doors==

Here's a step by step explanation on how to make sliding glass doors.

The following symbols are used:

<nowiki>*</nowiki> vertex
- ¦ red lines
= | / \ white lines

:STEP 1: Start by making the following sectors. All are valid player space.

*=============*
| | Sectors 'a' and 'e' are the corridor in which
| a | the door will be made.
*-------------*
| |
| b |
*-------------*
| |
| | Sector 'c' will be the actual door.
| |
| c |
*-------------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 2: Split sector 'c' in half.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
| ¦ |
| ¦ | Sector 'c1' and 'c2' are the two parts
| ¦ | of the door which will slide apart.
| c1 ¦ c2 |
*------*------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 3: Make sectors 'f' and 'g'.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ ¦ / | Make sure sectors 'f' and 'g' are valid player spaces.
|f * ¦ * g| (Alt-S in 2D mode).
| / c1 ¦ c2 \ |
|/ ¦ \|
*------*------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 4: Raise floor of sectors 'f' and 'g' and mask walls. Then lower floor again.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ ¦ / | Raise the floors of sectors 'f' and 'g' and for each sector
|f *v1 ¦ v2* g| mask one of the diagonal lines. In this example we'll mask
| / ¦ \ | <- these two diagonal lines. Mask them for example with 'glass2'.
|/ c1 ¦ c2 \| If you use 'glass1' you'll be able to break the glass and walk
*------*------* through the door without ever having to open it.
| v3 | Make the walls a bit translucent so you can see through them.
| d | Also make them blockable and hittable ('b' and 'Ctrl-H in 2D mode).
*-------------* Lower the floors again to the same height as the floors of sectors
| | 'c1' and 'c2'.
| e |
*=============* 'v1' 'v2' and 'v3' have been named for the next picture.

:STEP 5: Move vertices.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ c1 ¦ c2 / | 'v1' and 'v2' have been moved down onto 'v3' The three
|f \ ¦ / g| vertices are all in the same place. They do NOT connect.
| \ ¦ / |
| \ ¦ / |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 6: Place sector effectors, gpspeed and music sprites and give sector lotag. Give sectors 'c1' and 'c2' both a lotag of 25. Put sector effectors in sector c1 and c2. Make them point towards each other (',' and '.' key in 2D mode, angle 0 and 1024) and give them a lotag of 15. Give them the same unique hitag. Also put gpspeed sprites in sectors 'c1' and 'c2'. They determine how far the door will open. The largest grid in build is 512. Give the gpspeed sprites the correct value for the lotag. Finally you can put a music sprite in one of the door sectors ('c1' _or_ 'c2'). Don't put music sprites in both sectors. The lotag is the door sound when it opens or closes.

:STEP 7: Add vertices.

*=============*
| |
| a |
*-------------*
| |
| b |
v4 *------*------* v5
|\ ¦ /|
| \ c1 ¦ c2 / | Insert two new vertices on the diagonal lines.
|f \ ¦ / g| 'v4' and 'v5' have been named for the next picture.
| * ¦ * |
| \ ¦ / |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 8: Move 'v4' and 'v5' down.

*=============*
| |
| a |
*-------------*
| b |
| |
| * v6 |
| /!\ |
| / ¦ \ |
| / ¦ \ |
| / ¦ \ |
| / c1! c2 \ |
|/ ¦ \|
v4 *---* ¦ *---* v5
| f \ ¦ / g |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 9: Move 'v6' down.

*=============*
| |
| a |
*-------------*
| b |
| v6 | The little triangles in the middle are sectors
v4 *---*--*--*---* v5 'c1' and 'c2'.
| f \ ¦ / g |
v7 *------*------* v8
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 10: Move 'v4' 'v5' 'v7' and 'v8'.

*=============*
| |
| a |
v9 *-------------* v10
| b |
/ v6 \
v4 *-----*--*--*-----* v5 Move the vertices to the outside a bit.
| f \ ¦ / g |
v7 *--------*--------* v8
\ v1-3 /
| d |
v11 *-------------* v12
| |
| e |
*=============*

:STEP 11: Move 'v9' and 'v10' down, move 'v11' and 'v12' up.
*=============*
| a |
|v9 v6 |v10
v4 *-*---*--*--*---*-* v5 'v9' and 'v10' have been moved down. Sector 'b' has
| f \ ¦ / g | a width of 0. Same goes for vertices 'v11' and 'v12',
v7 *-*------*------*-* v8 they have been moved up. Sector 'd' also has a width
|v11 v12| of 0.
| |
| e |
*=============*

:STEP 12: Make sure sectors 'f' and 'g' aren't too wide or it will look ugly. If you want a vertical bar in the door (i.e. doorpost) just draw a non-valid player space in sector 'f' and/or 'g'. These non-valid player spaces will slide aside with the door so they are best put in the middle. You can of course also partially raise the floors of sectors 'f' and 'g' and lower the ceilings and still mask the wall (With any texture you like! :) )

==Alternate See-Through Sliding Doors==
''Map Name: [[Media:Altslidoor.map|Altslidoor.map]] (Room 2)''

The concept was originally posted by Ursurper in the Dukeworld forum, a very long time ago. It works for Mapster32, is efficient to make and very simple.

*Step 1: Make a sector that will be your entire door sector. It needs to be long enough to hold the sliding door itself and when the door is in the open position. Split (or mark) this sector in two if two sliding doors are to operate.
*Step 2: Create one child sector in the sector of step one, this will be the door itself.
* Step 3: To make a see-through door, choose a red wall of the door sector and press ''[m]'' to make a masked wall and ''[t]'' to define the transparency.
* Step 4: (Optional) Create as many sub sectors in the door sector as needed for a realistic looking door.
*Step 5: Give each sub-sector (except white islands) of the door sector a lotag of 25, and an SE sprite with a lowtag of 15 and a unique hitag. Point the tail of the SE to the same direction as the door will move when it closes.
*Step 6: Add a [[GPSPEED]] to this (those) sector(s) and set the the lotag to the distance the door is to travel.
*Step 7: Add a [[Music&SFX]] Sprite and if required, [[Activator]]s and switches to control the door.

Note 1: If you want to use a switch that opens two sliding doors (as in an elevator), place two [[Activator]] sprites in one door sector, and one in the other. Give all three [[Activator]]s the same unique lotag as the switch. 
Note 2: Any white wall sector for a door sector can only be an island sector. 
Note 3: Every Sub-Sector of the Door Sector operated by a switch has to have one [[Activator]]. If the total amount of [[Activator]]s are even, add one more Activator in one of the Door Sectors.

[[Category:Editing Doors]]

Sliding Doors

2012-04-20T00:42:57Z

Hank:

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.

==Sliding Doors==

''Map Name: [[Media:Advanced.map|ADVANCED.MAP]] (ROOM 1-C)''

Again, due to the extremely difficult task of explaining this how-to, I have provided a step by step example in the tutorial map, showing how to make this door. Just take a look at the example and it should make sense (it goes step by step in the building process).

==Alternate Sliding Doors==
''Map Name: [[Media:Altslidoor.map|Altslidoor.map]] (Room 1)''

The concept was originally posted by Ursurper in the Dukeworld forum, a very long time ago. It works for Mapster32, is efficient to make and very simple.

*Step 1: Make a sector that will be your entire door sector. It needs to be long enough to hold the sliding door itself and when the door is in the open position. Split (mark) this sector in two if two sliding doors are to operate.
*Step 2: Create one child sector in the sector of step one, this will be the door itself.
*Step 3: Give each door sector a lotag of 25, and an SE sprite with a lowtag of 15 and a unique hitag. Point the tail of the SE to the same direction as the door will move when it closes.
*Step 4: Add a [[GPSPEED]] to this sector and set the the lotag to the distance the door is to travel.
*Step 5: Add a [[Music&SFX]] Sprite and if required, [[Activator]]s and switches to control the door.

Note 1: If you want to use a switch that opens two sliding doors (as in a elevator), place two [[Activator]] sprites in one door sector, and one in the other. Give all three [[Activator]]s the same unique lotag as the switch.

==See Through Sliding Doors==

Here's a step by step explanation on how to make sliding glass doors.

The following symbols are used:

<nowiki>*</nowiki> vertex
- ¦ red lines
= | / \ white lines

:STEP 1: Start by making the following sectors. All are valid player space.

*=============*
| | Sectors 'a' and 'e' are the corridor in which
| a | the door will be made.
*-------------*
| |
| b |
*-------------*
| |
| | Sector 'c' will be the actual door.
| |
| c |
*-------------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 2: Split sector 'c' in half.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
| ¦ |
| ¦ | Sector 'c1' and 'c2' are the two parts
| ¦ | of the door which will slide apart.
| c1 ¦ c2 |
*------*------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 3: Make sectors 'f' and 'g'.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ ¦ / | Make sure sectors 'f' and 'g' are valid player spaces.
|f * ¦ * g| (Alt-S in 2D mode).
| / c1 ¦ c2 \ |
|/ ¦ \|
*------*------*
| |
| d |
*-------------*
| |
| e |
*=============*

:STEP 4: Raise floor of sectors 'f' and 'g' and mask walls. Then lower floor again.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ ¦ / | Raise the floors of sectors 'f' and 'g' and for each sector
|f *v1 ¦ v2* g| mask one of the diagonal lines. In this example we'll mask
| / ¦ \ | <- these two diagonal lines. Mask them for example with 'glass2'.
|/ c1 ¦ c2 \| If you use 'glass1' you'll be able to break the glass and walk
*------*------* through the door without ever having to open it.
| v3 | Make the walls a bit translucent so you can see through them.
| d | Also make them blockable and hittable ('b' and 'Ctrl-H in 2D mode).
*-------------* Lower the floors again to the same height as the floors of sectors
| | 'c1' and 'c2'.
| e |
*=============* 'v1' 'v2' and 'v3' have been named for the next picture.

:STEP 5: Move vertices.

*=============*
| |
| a |
*-------------*
| |
| b |
*------*------*
|\ ¦ /|
| \ c1 ¦ c2 / | 'v1' and 'v2' have been moved down onto 'v3' The three
|f \ ¦ / g| vertices are all in the same place. They do NOT connect.
| \ ¦ / |
| \ ¦ / |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 6: Place sector effectors, gpspeed and music sprites and give sector lotag. Give sectors 'c1' and 'c2' both a lotag of 25. Put sector effectors in sector c1 and c2. Make them point towards each other (',' and '.' key in 2D mode, angle 0 and 1024) and give them a lotag of 15. Give them the same unique hitag. Also put gpspeed sprites in sectors 'c1' and 'c2'. They determine how far the door will open. The largest grid in build is 512. Give the gpspeed sprites the correct value for the lotag. Finally you can put a music sprite in one of the door sectors ('c1' _or_ 'c2'). Don't put music sprites in both sectors. The lotag is the door sound when it opens or closes.

:STEP 7: Add vertices.

*=============*
| |
| a |
*-------------*
| |
| b |
v4 *------*------* v5
|\ ¦ /|
| \ c1 ¦ c2 / | Insert two new vertices on the diagonal lines.
|f \ ¦ / g| 'v4' and 'v5' have been named for the next picture.
| * ¦ * |
| \ ¦ / |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 8: Move 'v4' and 'v5' down.

*=============*
| |
| a |
*-------------*
| b |
| |
| * v6 |
| /!\ |
| / ¦ \ |
| / ¦ \ |
| / ¦ \ |
| / c1! c2 \ |
|/ ¦ \|
v4 *---* ¦ *---* v5
| f \ ¦ / g |
*------*------*
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 9: Move 'v6' down.

*=============*
| |
| a |
*-------------*
| b |
| v6 | The little triangles in the middle are sectors
v4 *---*--*--*---* v5 'c1' and 'c2'.
| f \ ¦ / g |
v7 *------*------* v8
| v1-3 |
| d |
*-------------*
| |
| e |
*=============*

:STEP 10: Move 'v4' 'v5' 'v7' and 'v8'.

*=============*
| |
| a |
v9 *-------------* v10
| b |
/ v6 \
v4 *-----*--*--*-----* v5 Move the vertices to the outside a bit.
| f \ ¦ / g |
v7 *--------*--------* v8
\ v1-3 /
| d |
v11 *-------------* v12
| |
| e |
*=============*

:STEP 11: Move 'v9' and 'v10' down, move 'v11' and 'v12' up.
*=============*
| a |
|v9 v6 |v10
v4 *-*---*--*--*---*-* v5 'v9' and 'v10' have been moved down. Sector 'b' has
| f \ ¦ / g | a width of 0. Same goes for vertices 'v11' and 'v12',
v7 *-*------*------*-* v8 they have been moved up. Sector 'd' also has a width
|v11 v12| of 0.
| |
| e |
*=============*

:STEP 12: Make sure sectors 'f' and 'g' aren't too wide or it will look ugly. If you want a vertical bar in the door (i.e. doorpost) just draw a non-valid player space in sector 'f' and/or 'g'. These non-valid player spaces will slide aside with the door so they are best put in the middle. You can of course also partially raise the floors of sectors 'f' and 'g' and lower the ceilings and still mask the wall (With any texture you like! :) )

==Alternate See-Through Sliding Doors==
''Map Name: [[Media:Altslidoor.map|Altslidoor.map]] (Room 2)''

The concept was originally posted by Ursurper in the Dukeworld forum, a very long time ago. It works for Mapster32, is efficient to make and very simple.

*Step 1: Make a sector that will be your entire door sector. It needs to be long enough to hold the sliding door itself and when the door is in the open position. Split (or mark) this sector in two if two sliding doors are to operate.
*Step 2: Create one child sector in the sector of step one, this will be the door itself.
* Step 3: To make a see-through door, choose a red wall of the door sector and press ''[m]'' to make a masked wall and ''[t]'' to define the transparency.
* Step 4: (Optional) Create as many sub sectors in the door sector as needed for a realistic looking door.
*Step 5: Give each sub-sector (except white islands) of the door sector a lotag of 25, and an SE sprite with a lowtag of 15 and a unique hitag. Point the tail of the SE to the same direction as the door will move when it closes.
*Step 6: Add a [[GPSPEED]] to this (those) sector(s) and set the the lotag to the distance the door is to travel.
*Step 7: Add a [[Music&SFX]] Sprite and if required, [[Activator]]s and switches to control the door.

Note 1: If you want to use a switch that opens two sliding doors (as in an elevator), place two [[Activator]]s sprites in one door sector, and one in the other. Give all three [[Activator]]s the same unique lotag as the switch. 
Note 2: Any white wall sector for a door sector can only be an island sector. 
Note 3: Every Sub-Sector of the Door Sector operated by a switch has to have one [[Activator]]. If the total amount of [[Activator]]s are even, add one more Activator in one of the Door Sectors.

[[Category:Editing Doors]]

File:Altslidoor.map

2012-04-19T04:59:22Z

Hank: Hank uploaded a new version of "File:Altslidoor.map": Added two distinct See-Thru type door set-ups

Alternate Sliding and See-Through Sliding Door

Sliding Doors

2012-04-18T03:30:44Z

Hank: /* Alternate Sliding Doors */

File:Altslidoor.map

2012-04-18T03:20:04Z

Hank: Alternate Sliding and See-Through Sliding Door

Alternate Sliding and See-Through Sliding Door

Sliding Doors

2012-04-17T05:45:07Z

Hank:

User talk:Hendricks266

2012-04-15T06:42:38Z

Hank:

== Administrative Requests ==
Feel free to add requests here if you want a change made to the wiki that is restricted to administrators. Use a level three heading for each issue, like this:

<nowiki>=== Request: ... ===</nowiki>

=== Request: Locked/Keycard Doors and Doors/Switch Categories ===
How about one more 'blank' sub header under Doors, [[:Category:Editing Doors]] ?

I want to change the title from Locked Doors to Keycard Doors, and make one named Locked Doors to describe various locked/unlock door set ups. Then I think all of [[:Category:Editing Switch Effects]] should be integrated to the door section.

Hopefully I posted this right.

Cheers - Hank

:I moved Locked Doors to [[Keycard Doors]] for you... everything else you should be able to take care of yourself. I see no protections on any of these pages. -[[User:Hendricks 266|Hendricks266]] ([[User talk:Hendricks 266|talk]]) 16:49, 10 April 2012 (PDT)

:: Thanks - Yet I can not add another chapter under doors; in this case a bold L and a title Locked Doors, and describe all normal and trick type arrangements for doors. Or we simply provide a link at the bottom of the door section (Pages in category "Editing Doors") to Editing Switch Effects page and I edit that. {that too I can not do}
:: Cheers [[User:Hank|Hank]] ([[User talk:Hank|talk]]) 19:28, 12 April 2012 (PDT)
:::Categories are managed by the MediaWiki software. You put articles in categories by adding the syntax for it in their own pages. I created a new [[Locked Doors]] page for you to edit which now shows up in [[:Category:Editing Doors]] because I specified it, which you can see when you edit the page. I added [[:Category:Editing Switch Effects]] to [[:Category:Editing Doors]] as well. Cheers! -[[User:Hendricks 266|Hendricks266]] ([[User talk:Hendricks 266|talk]]) 01:20, 13 April 2012 (PDT)
::::BTW, watching pages simply makes them bold in [[Special:RecentChanges]]. -[[User:Hendricks 266|Hendricks266]] ([[User talk:Hendricks 266|talk]]) 01:23, 13 April 2012 (PDT)

::: Many thanks. The info is now updated. I planed to place it into Locked Doors, but have second thoughts. Currently it is linked to Switch Effects on the front page. We can not have two titles for the same material. It's a decision you need to do. - Keep the status quo and link Locked Doors to Switch Effects, or deleting Switch Effects all together and place all the text into Locked Doors, or whatever else you think is appropiate. Either way, Doors are now up to date. Cheers [[User:Hank|Hank]] ([[User talk:Hank|talk]]) 23:42, 14 April 2012 (PDT)

Locked Doors

2012-04-15T06:22:40Z

Hank: Replaced content with " Category:Editing Doors"

[[Category:Editing Doors]]

Category:Editing Multiplayer Level Making

2012-04-15T06:21:41Z

Hank:

Locked Doors

2012-04-15T01:33:41Z

Hank:

A single player style map is most of the time different to a multiplayer style map. If you plan to make maps incorporating both styles, all locked pathways should to be operable for mulitplayer, at all time.

* Step 1. Construct the locked path.
* Step 2. Add an additional switch and set the color palette to 1. The switch is then only visible in Multiplayer.
* Step 3. Match the lowtag of the switch to the lowtag of the element1 controlling the locking mechanism2.

To see how it is done, simply open any original Duke 3D map.

1) [[Activator]], [[Activatorlocked|Activator Locked]], [[Keycard Doors|Keycard]], [[Walls and Wall Effects#Forcefields and Controlling Them|Force Field]] and [[Masterswitch]]. 
2) [[Locked Lifts|Elevator]], [[Doors]], [[Walls and Wall Effects#Forcefields and controlling them|Force Field]] and more.

[[Category:Editing Doors]]

Locked Doors

2012-04-15T01:27:54Z

Hank: /* Locked Doors */

A single player style map and a multiplayer map are different in modern style maps. If you plan to make maps incorporating both styles, all locked pathways should to be operable for mulitplayer, at all time.

* Step 1. Construct the locked path.
* Step 2. Add an additional switch and set the color palette to 1. The switch is then only visible in Multiplayer.
* Step 3. Match the lowtag of the switch to the lowtag of the element1 controlling the locking mechanism2.

To see how it is done, simply open any original Duke 3D map.

1) [[Activator]], [[Activatorlocked|Activator Locked]], [[Keycard Doors|Keycard]], [[Walls and Wall Effects#Forcefields and Controlling Them|Force Field]] and [[Masterswitch]]. 
2) [[Locked Lifts|Elevator]], [[Doors]], [[Walls and Wall Effects#Forcefields and controlling them|Force Field]] and more.

[[Category:Editing Doors]]

Locked Doors

2012-04-14T22:42:06Z

Hank:

A single player style map and a multiplayer map is different in modern style maps. If you plan to make maps incorporating both styles, all locked pathways should to be operable for mulitplayer, at all time.

* Step 1. Construct the locked path.
* Step 2. Add an additional switch and set the color palette to 1. The switch is then only visible in Multiplayer.
* Step 3. Match the lowtag of the switch to the lowtag of the element1 controlling the locking mechanism2.

To see how it is done, simply open any original Duke 3D map.

1) [[Activator]], [[Activatorlocked|Activator Locked]], [[Keycard Doors|Keycard]], [[Walls and Wall Effects#Forcefields and Controlling Them|Force Field]] and [[Masterswitch]]. 
2) [[Locked Lifts|Elevator]], [[Doors]], [[Walls and Wall Effects#Forcefields and controlling them|Force Field]] and more.

[[Category:Editing Doors]]

Locked Doors

2012-04-14T22:17:40Z

Hank:

A single player style map and a multiplayer map is different in modern style maps. If you plan to make maps incorporating both styles, all locked pathways should to be operable for mulitplayer, at all time.

* Step 1. Construct the locked path.
* Step 2. Add an additional switch and set the color palette to 1. The switch is then only visible in Multiplayer.
* Step 3. Match the lowtag of the switch to the lowtag of the element1 controlling the locking mechanism2.

To see how it is done, simply open any original Duke 3D map.

1) [[Activator]], [[Activatorlocked|Activator Locked]], [[Keycard Doors|Keycard]], [[Walls and Wall Effects#Forcefields and Controlling Them|Force Field]] and [[Masterswitch]]. 
2) [[Locked Lifts|Elevator]], [[Doors]], [[Walls and wall effects#forcefields and controlling them|Force Field]] and more.

[[Category:Editing Doors]]

Category:Editing Switch Effects

2012-04-14T19:37:06Z

Hank: /* Switch Activated Doors */

Category:Editing Switch Effects

2012-04-14T19:03:49Z

Hank: /* Multi-Door Switches */

Category:Editing Switch Effects

2012-04-14T18:51:19Z

Hank: /* Combination Door Switches */

Category:Editing Switch Effects

2012-04-14T18:41:06Z

Hank: /* Switch Activated Doors */

User talk:Hendricks266

2012-04-13T02:28:51Z

Hank: /* Hank's Locked/Keycard Doors Request */

User talk:Hendricks266

2012-04-13T02:28:23Z

Hank: /* Hank's Locked/Keycard Doors Request */

Category:Editing Lighting Effects

2012-04-13T02:08:22Z

Hank: /* Pulsating Lights */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Making Lights Blink==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-B)''

Blinking lights can add a great mood and sense of environment in any user level. This effect makes lights blink randomly.

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting.

:STEP 2: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 4, and a unique hitag value. The hitag value is the flash randomizing number, so use any value you want.

:STEP 3: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 1:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 2:'' This effect can *not* be used with the light switch effect.

''NOTE 3:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Making Lights Blink When Shot==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-C)''

This effect allows you to cause a light to flash randomly once it is broken by the player (by the player shooting the light).

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting. If you are constructing a light in a wall, make sure that you lower the ceiling of the light sector to the floor, placing the light texture on the wall face that appears once you lower the sector ceiling to the floor.

:::''NOTE 1:'' The light texture that you use, should be breakable (i.e. - when you shoot the light, the light texture should change to the corresponding broken light texture).

:STEP 2: If you are creating a ceiling light, give the light sector a unique sector hitag value. If you are creating a wall light, give the red wall that separates the light sector from the wall sector a unique wall lotag value.

:STEP 3: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 3. If you are creating a wall light, give the sector effector sprite a hitag value equal to the wall's lotag value. If you are creating a ceiling light, give the sector effector sprite a hitag value equal to the light sector's hitag value.

:STEP 4: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 2:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 3:'' This effect *can* be used with the light switch effect.

''NOTE 4:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Open Door & Room Lights Up==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-D)''

This effect allows rooms to light up when a door is opened (assuming that light would come in the door).

:STEP 1: Construct the door and the sectors that you wish to light up.

:STEP 2: Place one sector effector sprite in the door and in each sector that you want to light up.

:STEP 3: Change the shade of each sector effector to the shade you want the sector it is located in to be when the door is open. Do this by moving the mouse over the sprite, and press the [']+[S] keys in 3D mode.

:STEP 4: Change the shade of each wall, ceiling, and floor of the sectors you want to light up to the value you want them to be when the door is closed.

:STEP 5: Give each sector effector sprite a lotag value of 8 and the same, unique hitag value. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Light Switches==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-E)''

This effect allows you to create a light switch from which the player can toggle a light on or off.

:STEP 1: Place a switch sprite (#712 is the standard light switch) somewhere in your level. Give this sprite a unique lotag value.

:STEP 2: Place one sector effector sprite in each sector that will light up when the light is on. The shade of this sprite determines how bright the light will be in that sprite's particular sector when the light is on.

:STEP 3: The shade of all walls, ceilings, and floors of the sectors to be lit up should be set to the shade they will be when the light is turned off.

:STEP 4: Give each sector effector sprite a lotag value of 12. Give each sector effector sprite the same hitag value that you gave to the light switch. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Colored Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-F)

To create colored lights, simply change the palette of the walls, floors, and ceilings you desire to be colored to one of the following values (palette is set in 3D mode by pressing the ''[ALT]''+''[P]'' keys when the mouse is over the desired object to change):

:* 1 = Blue
:* 2 = Red
:* 7 = Yellow
:* 8 = Green

==Pulsating Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-G)

Pulsating lights can be used to create some neat effects (moving lights to name one).

:STEP 1: Place a [[Cycler]] sprite in the sector(s) that you want the light to pulsate in. Change the shade of this sprite to how bright you want the light to be when the light is at its brightest point.

:STEP 2: Change the shade of the floor to how dark the sector should be when the light is at its darkest point.

:STEP 3: To change the speed of the light pulsing, simply place one [[GPSpeed]] sprite in the same sector as the [[Cycler]] sprite. Now give the [[GPSpeed]] sprite a lotag value. This value is how fast or slow the light will pulsate (the higher the value, the faster the light will pulsate).
:STEP 4: To turn the effect off/on, give a switch or [[Touchplate]] a unique Lotag value and match the Hitag of each [[Cycler]] sprite.

''NOTE 1:'' Here is a great bit of information on the speed of Cycler sprites when combined with [[GPSpeed]] sprites (thanks to Keith Tyson for this information). The cycle length (going from bright to dark to bright again) seems to be halved as the [[GPSpeed]] lotag value is doubled. Strangely enough, this is the case up to a value of 1023, (a value of 1024 doesn't work). From 1025 to 2047, the above pattern is reversed: As the [[GPSpeed]] lotag value gets higher, the cycle length increases. A value of 2048 doesn't work either. A simple conversion indicates that a lotag of 1 will produce roughly one cycle in 120 seconds (quite slow), while a lotag of 1023 will produce roughly 8 cycles per second (quite fast).

''NOTE 2:'' Walls with a hitag value of 1 are not affected by the [[Cycler]] sprite.

''NOTE 3:'' This effect can be used to create the "rotating" lights found in some of the episode 2 levels. Take a look at those levels to see how this is done.

Category:Editing Lighting Effects

2012-04-13T02:05:38Z

Hank: /* Pulsating Lights */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Making Lights Blink==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-B)''

Blinking lights can add a great mood and sense of environment in any user level. This effect makes lights blink randomly.

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting.

:STEP 2: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 4, and a unique hitag value. The hitag value is the flash randomizing number, so use any value you want.

:STEP 3: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 1:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 2:'' This effect can *not* be used with the light switch effect.

''NOTE 3:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Making Lights Blink When Shot==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-C)''

This effect allows you to cause a light to flash randomly once it is broken by the player (by the player shooting the light).

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting. If you are constructing a light in a wall, make sure that you lower the ceiling of the light sector to the floor, placing the light texture on the wall face that appears once you lower the sector ceiling to the floor.

:::''NOTE 1:'' The light texture that you use, should be breakable (i.e. - when you shoot the light, the light texture should change to the corresponding broken light texture).

:STEP 2: If you are creating a ceiling light, give the light sector a unique sector hitag value. If you are creating a wall light, give the red wall that separates the light sector from the wall sector a unique wall lotag value.

:STEP 3: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 3. If you are creating a wall light, give the sector effector sprite a hitag value equal to the wall's lotag value. If you are creating a ceiling light, give the sector effector sprite a hitag value equal to the light sector's hitag value.

:STEP 4: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 2:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 3:'' This effect *can* be used with the light switch effect.

''NOTE 4:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Open Door & Room Lights Up==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-D)''

This effect allows rooms to light up when a door is opened (assuming that light would come in the door).

:STEP 1: Construct the door and the sectors that you wish to light up.

:STEP 2: Place one sector effector sprite in the door and in each sector that you want to light up.

:STEP 3: Change the shade of each sector effector to the shade you want the sector it is located in to be when the door is open. Do this by moving the mouse over the sprite, and press the [']+[S] keys in 3D mode.

:STEP 4: Change the shade of each wall, ceiling, and floor of the sectors you want to light up to the value you want them to be when the door is closed.

:STEP 5: Give each sector effector sprite a lotag value of 8 and the same, unique hitag value. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Light Switches==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-E)''

This effect allows you to create a light switch from which the player can toggle a light on or off.

:STEP 1: Place a switch sprite (#712 is the standard light switch) somewhere in your level. Give this sprite a unique lotag value.

:STEP 2: Place one sector effector sprite in each sector that will light up when the light is on. The shade of this sprite determines how bright the light will be in that sprite's particular sector when the light is on.

:STEP 3: The shade of all walls, ceilings, and floors of the sectors to be lit up should be set to the shade they will be when the light is turned off.

:STEP 4: Give each sector effector sprite a lotag value of 12. Give each sector effector sprite the same hitag value that you gave to the light switch. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Colored Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-F)

To create colored lights, simply change the palette of the walls, floors, and ceilings you desire to be colored to one of the following values (palette is set in 3D mode by pressing the ''[ALT]''+''[P]'' keys when the mouse is over the desired object to change):

:* 1 = Blue
:* 2 = Red
:* 7 = Yellow
:* 8 = Green

==Pulsating Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-G)

Pulsating lights can be used to create some neat effects (moving lights to name one).

:STEP 1: Place a [[Cycler]] sprite in the sector(s) that you want the light to pulsate in. Change the shade of this sprite to how bright you want the light to be when the light is at its brightest point.

:STEP 2: Change the shade of the floor to how dark the sector should be when the light is at its darkest point.

:STEP 3: To change the speed of the light pulsing, simply place one [[GPSpeed]] sprite in the same sector as the [[Cycler]] sprite. Now give the [[GPSpeed]] sprite a lotag value. This value is how fast or slow the light will pulsate (the higher the value, the faster the light will pulsate).
:STEP 4: To turn the effect off/on, give a switch or [[Touchplate]] a unique Lotag and match each Hitag of the [[Cycler]] sprites.

''NOTE 1:'' Here is a great bit of information on the speed of Cycler sprites when combined with [[GPSpeed]] sprites (thanks to Keith Tyson for this information). The cycle length (going from bright to dark to bright again) seems to be halved as the [[GPSpeed]] lotag value is doubled. Strangely enough, this is the case up to a value of 1023, (a value of 1024 doesn't work). From 1025 to 2047, the above pattern is reversed: As the [[GPSpeed]] lotag value gets higher, the cycle length increases. A value of 2048 doesn't work either. A simple conversion indicates that a lotag of 1 will produce roughly one cycle in 120 seconds (quite slow), while a lotag of 1023 will produce roughly 8 cycles per second (quite fast).

''NOTE 2:'' Walls with a hitag value of 1 are not affected by the [[Cycler]] sprite.

''NOTE 3:'' This effect can be used to create the "rotating" lights found in some of the episode 2 levels. Take a look at those levels to see how this is done.

Category:Editing Lighting Effects

2012-04-13T01:57:42Z

Hank: /* Pulsating Lights */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Making Lights Blink==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-B)''

Blinking lights can add a great mood and sense of environment in any user level. This effect makes lights blink randomly.

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting.

:STEP 2: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 4, and a unique hitag value. The hitag value is the flash randomizing number, so use any value you want.

:STEP 3: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 1:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 2:'' This effect can *not* be used with the light switch effect.

''NOTE 3:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Making Lights Blink When Shot==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-C)''

This effect allows you to cause a light to flash randomly once it is broken by the player (by the player shooting the light).

:STEP 1: Create a light sector. This sector can either be in a wall, or a ceiling light sector, but it needs to be a sector. Take a look at the tutorial map to see examples of both types of lighting. If you are constructing a light in a wall, make sure that you lower the ceiling of the light sector to the floor, placing the light texture on the wall face that appears once you lower the sector ceiling to the floor.

:::''NOTE 1:'' The light texture that you use, should be breakable (i.e. - when you shoot the light, the light texture should change to the corresponding broken light texture).

:STEP 2: If you are creating a ceiling light, give the light sector a unique sector hitag value. If you are creating a wall light, give the red wall that separates the light sector from the wall sector a unique wall lotag value.

:STEP 3: Place one sector effector sprite in each sector you want to light up. Give these sprites a lotag value of 3. If you are creating a wall light, give the sector effector sprite a hitag value equal to the wall's lotag value. If you are creating a ceiling light, give the sector effector sprite a hitag value equal to the light sector's hitag value.

:STEP 4: Set the shade of the walls, floor, and ceiling near your light to the shade value you want it to be when the lights are off. Then, set the shade of the sector effector sprites to the shade value you want it to be when the lights are on. You set the shade value by pressing the [']+[S] key on the desired wall, ceiling, or floor in 3D mode. You are finished - Look at the tutorial map if you don't quite understand.

''NOTE 2:'' You can make colored blinking lights as well. Simply give the sector effector sprites a palette value equal to the color that you want the light to be when flashing. Both the sectors and the sector effector sprites can have different palette values.

''NOTE 3:'' This effect *can* be used with the light switch effect.

''NOTE 4:'' To prevent one side of a red line in 2D mode (a 2 sided wall) from being affected by the light effect, give the side of the wall you want to not be affected a wall hitag value of 1.

==Open Door & Room Lights Up==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-D)''

This effect allows rooms to light up when a door is opened (assuming that light would come in the door).

:STEP 1: Construct the door and the sectors that you wish to light up.

:STEP 2: Place one sector effector sprite in the door and in each sector that you want to light up.

:STEP 3: Change the shade of each sector effector to the shade you want the sector it is located in to be when the door is open. Do this by moving the mouse over the sprite, and press the [']+[S] keys in 3D mode.

:STEP 4: Change the shade of each wall, ceiling, and floor of the sectors you want to light up to the value you want them to be when the door is closed.

:STEP 5: Give each sector effector sprite a lotag value of 8 and the same, unique hitag value. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Light Switches==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-E)''

This effect allows you to create a light switch from which the player can toggle a light on or off.

:STEP 1: Place a switch sprite (#712 is the standard light switch) somewhere in your level. Give this sprite a unique lotag value.

:STEP 2: Place one sector effector sprite in each sector that will light up when the light is on. The shade of this sprite determines how bright the light will be in that sprite's particular sector when the light is on.

:STEP 3: The shade of all walls, ceilings, and floors of the sectors to be lit up should be set to the shade they will be when the light is turned off.

:STEP 4: Give each sector effector sprite a lotag value of 12. Give each sector effector sprite the same hitag value that you gave to the light switch. You are now finished - Take a look at the tutorial map if you don't quite understand.

==Colored Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-F)

To create colored lights, simply change the palette of the walls, floors, and ceilings you desire to be colored to one of the following values (palette is set in 3D mode by pressing the ''[ALT]''+''[P]'' keys when the mouse is over the desired object to change):

:* 1 = Blue
:* 2 = Red
:* 7 = Yellow
:* 8 = Green

==Pulsating Lights==

Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 2-G)

Pulsating lights can be used to create some neat effects (moving lights to name one).

:STEP 1: Place a [[Cycler]] sprite in the sector(s) that you want the light to pulsate in. Change the shade of this sprite to how bright you want the light to be when the light is at its brightest point.

:STEP 2: Change the shade of the floor to how dark the sector should be when the light is at its darkest point.

:STEP 3: To change the speed of the light pulsing, simply place one [[GPSpeed]] sprite in the same sector as the [[Cycler]] sprite. Now give the [[GPSpeed]] sprite a lotag value. This value is how fast or slow the light will pulsate (the higher the value, the faster the light will pulsate).
:STEP 4: To make that effect operable with a switch or [[Touchplate]], give the switch a unique Lotag and match each Hitag of the [[Cycler]] sprites.

''NOTE 1:'' Here is a great bit of information on the speed of Cycler sprites when combined with [[GPSpeed]] sprites (thanks to Keith Tyson for this information). The cycle length (going from bright to dark to bright again) seems to be halved as the [[GPSpeed]] lotag value is doubled. Strangely enough, this is the case up to a value of 1023, (a value of 1024 doesn't work). From 1025 to 2047, the above pattern is reversed: As the [[GPSpeed]] lotag value gets higher, the cycle length increases. A value of 2048 doesn't work either. A simple conversion indicates that a lotag of 1 will produce roughly one cycle in 120 seconds (quite slow), while a lotag of 1023 will produce roughly 8 cycles per second (quite fast).

''NOTE 2:'' Walls with a hitag value of 1 are not affected by the [[Cycler]] sprite.

''NOTE 3:'' This effect can be used to create the "rotating" lights found in some of the episode 2 levels. Take a look at those levels to see how this is done.

User talk:Hendricks266

2012-04-13T00:24:08Z

Hank: /* Hank's Locked/Keycard Doors Request */

Category:Editing Sectors That Rise and Fall

2012-04-11T03:10:32Z

Hank: /* Constructing Destructible Buildings */

{{Build Intro}}
NOTE: Much of information on this page is from around 1999. Some may be outdated, and some may be incorrect -- this page exists to get you started with the Level Editing and may not currently cover some of the additional features available in Mapster32.
__NOTOC__
==Lifts==

STEP 1. Build your lift sector. You need to make sure it has an upper floor and a lower floor connecting to it, otherwise it will not work correctly.

STEP 2. Give the lift sector one of the following sector tags:
:: '''16'''- lift starts at the top floor. Only the floor of the lift moves, the ceiling does not.
:: '''17'''- lift starts at the bottom floor. Only the floor of the lift moves, the ceiling does not.
:: '''18'''- lift starts at the top floor. Both floor and ceiling move.
:: '''19'''- lift starts at the bottom floor. Both floor and ceiling move.

STEP 3. Add a [[Music&SFX]] sprite to the lift sector. The lotag of the Music&SFX plays when the lift is activated, and the hitag plays when the lift arrives at its destination. Add a [[GPSPEED]] sprite to the lift sector to control its speed.

==Switch Operated Lifts==

It is possible have a lift operated by a switch. Simply build a lift as normal. Then add an [[activator]] to the lift sector, and give it a unique lotag. Add a switch somewhere and give it the same lotag as you gave the activator. Now the lift can only be operated by hitting the switch.

==Locked Lifts==

Simply build a lift as normal, and place an [[activatorlocked]] in it. Give the activatorlocked a unique lotag, and place an accesscard lock somewhere with the same lotag. Unfortunately this cannot be combined with a switch-activated lift, because hitting the switch will activate the lift whether it is locked or not.

==Elevator Transports==

This simulates true level-over-level by warping you from one elevator sector to the other.

STEP 1: Build your two elevator sectors. There needs to be one for the upper floor and one for the lower floor. You need to make them the exact same size and shape, and the distance between the floor and ceiling needs to be exactly the same. It's recommended, but not necessary, to have the same textures and shading as well- but if you want an effect like the lights suddenly turning off half-way down that is definitely OK. You also need to make sure that the lower floor is physically below the upper one; the elevator will actually travel the whole vertical distance between the two floors.

STEP 2: Tag both elevator sectors with a lotag of 15. Place a [[sectoreffector]] with a lotag of 17 in both elevator sectors, and make sure they are in the exact same place in both sectors. Give both sectoreffectors the same unique hitag.

STEP 3: Decide which floor the elevator should start at. Give the sectoreffector in that sector a shade that's darker than the shade of the other one. 32 or 64 are good values. Give the sector that the elevator does ''not'' start at a hitag of 1.

STEP 4: You will need to fiddle with the alignment of the textures in the elevator shaft to make sure they transition smoothly during the effect. This can be time-consuming but if you don't do it it looks amateurish.

==Constructing Destructible Buildings==

''Map Name: [[Media:Tutorial.map|TUTORIAL.MAP]] (ROOM 5-G)''
* STEP 1: Create the building sectors (that will blow up) and make them look as if the building has already been destroyed. Place one sector-effector sprite, one Masterswitch sprite, and one GPSpeed sprite in each sector that will be affected.

* STEP 2: Give the GPSpeed a lotag value of how fast you want the building to lower during its destruction (a value of 64 was used for E1L2 map). Give the sector effector sprite a lotag value of 13, and a unique hitag value. Then give the Masterswitch sprite a lotag value equal to the sector effector hitag, and a hitag delay value, unless the building is to collapse at the same instant the explosions happen.

* STEP 3: Place a switch or Touchplate somewhere in your level. Give it a lotag value equal to the Sector-effector hitag.

* STEP 4: Place some C-9 sprites around your building, giving each a hitag value equal to the sector effector hitag value. Then set a lotag value for each C-9 sprite (this value is the delay before the C-9 sprite will explode). Remember to make the C-9 sprites as skinny as you can in the x direction (use the [4] key on the keypad).

NOTE 1: A Masterswitch sprite should be in each sector that a C-9 sprite exists. If this is not the case, the C-9 sprites will not explode.

==Crushers (Engine Pistons)==

This is a sector whose ceiling repeatedly lowers to the ground and then raises back to its original height. Place a sectoreffector in it with a lotag of 25. If you like, add a GPSPEED sprite to regulate its speed: a GPSPEED lotag of 256 is the default and gives very rapid movement.

You can slope the floor and ceiling but the piston will still crush you even if this leaves enough room to stand.

==Making the Ceiling Fall Upon an Explosion==

This effect is not used in the game, but is fully functional. It causes the ceiling to drop if an explosion occurs in the sector.

STEP 1. Build the sector that you want to have a dropping ceiling.

STEP 2. Put a [[sectoreffector]] with a lotag of 19 in the sector.

STEP 3. Put a [[GPSPEED]] in the sector to control the rate at which the ceiling falls.

==Rotating & Rising Sectors==

STEP 1. Build a sector that you would like to rotate. Place a [[sectoreffector]] and an [[activator]] in it. Give the sectoreffector a unique hitag, and give the activator that number as its lotag. Place another sectoreffector anywhere in your level; this will be the point around which the sector will rotate. Give it a lotag of 1 and the same hitag as the SE0 in the rotating sector.

STEP 2. Lower the rotating sector to as low as it will ever go, and give it a lotag of 30. Raise the SE0 to as high as the rotating sector will ever go. Put in a [[Music&SFX]] if you want it to make a sound.

STEP 3. The angle of the SE0 controls the direction of rotation. Have it pointing north if you want it to go clockwise, and pointing south for counter-clockwise.

STEP 4. Both the speed at which the sector raises and the time it takes to perform a rotation are fixed. There is no way to influence them. You can use a [[GPSPEED]] sprite to control the speed of rotation, which turns out to determine the ''amount'' of rotation because the time is fixed. The default, if you leave out the GPSPEED, is 256- this corresponds to a one quarter rotation. So if you want the rotate-rise bridge to do a three-quarter turn you would give the GPSPEED a lotag of 256 x 3 = 768.

NOTE. For some reason this effect only works correctly if you have at least one other SE controlled effect in your level. If the rotate-rise bridge is the ONLY effect in your level then it will stupidly treat the SE0 as the pivot sprite.

==Making Ceilings and Floors Drop Down==

This effect is used to simulate a ceiling to cave in or floor to sink. This event takes place once, only.

Step 1 Tag each sector to be affected with Low Tag 28.

Step 2 Give each sector an Activator, Speed and SE21 sprite.

Step 3 If the floor is to fall, point the tail of SE 21 down and position the SE sprite to where the floor is to be at game start and lower the floor to where it should be when the effect took place.

Step 4 If the ceiling is to cave in, position the ceiling to where it should be at game start and position the SE 21 sprite to where the ceiling is to be when the effect took place.

Step 5 Set the Speed sprite to a desired speed. (+ 3000 for fast action)

Step 6 Match the Low Tag of the Activator with the Low Tag of a switch or Touchplate.

==Incremental Rising and Falling Sectors (v. 1.4 or 1.5 Required)==
''Map Name: [[Media:Atomic.map|ATOMIC.MAP]] (ROOM #3)''

This effect is used most often in Duke-Tag levels for showing the team score incrementally. It raises or lowers a sector incrementally by flipping a switch several times (or toggling some other trigger in the level).

STEP 1: Create the sector that will rise or fall when activated.

STEP 2: Place one sector effector sprite in this sector. Give this sprite a lotag of 18 and a hitag equal to the amount of units moved per activation (one unit is equal to 1 [PGUP] or [PGDN] in Mapster32).

Step 3: Now, set the angle for which part of the sector you want to move. Up makes the floor rise or fall, while down makes the ceiling rise or fall.

Step 4: Set the palette color of the SE sprite. A value of 0 starts the sector at the height you set it at in Mapster32, and it rises or falls to the sector effector's height. Anything other than 0 starts the sector at the height of the sector effector and lowers or raises it to the adjacent sector's height.

STEP 5: Place a switch (or other trigger) somewhere in your level, and give it a unique lotag.

STEP 6: Place one activator sprite in the rising (or falling) sector and give it the same lotag as the switch.

(Comment from the original author: "You'll have to play around with it to get it just right").

==Constructing Complex Doors with SE31 and SE32==

To build a split door that does not have one even horizontal sector, using tile 449 as a sample.

STEP 1. Make as many sectors as needed, side by side, and set up the complete door at when the door is in the Door Open position. It will take a while to match the tile with the slopes and size of the sectors.

STEP 2. Add to each sector an Activator, Speed and two SE sprites.

STEP 3. Position each SE sprite to line up where the Door Closed position shall be. Tag one of the two SE sprites with Low Tag 31 and the other Low Tag 32. Rotate the tail of tho two SE sprites to point straight down.

STEP 4. Set the Low Tag of the Activator sprite to a Low Tag of a Switch, Touchplate or Wall. Set the Speed sprite to a desired speed.

[[Image:Door3132a.gif]] [[Image:Door3132c.gif]]

Notes:

1. At play time, when the sector with SE31/SE32 sprites is first activated: If the tail points up, the sector will move from its elevation, set during construction, towards the elevation of the SE sprite. If the tail points down, the sector will be on the same level as the SE sprite and move towards its elevation set during construction.

2. Make sure that bottom of the the SE sprites match the First Wall vertices.

3. If you use a designated door tile (listed in the def.con) you can also set the Low Tag of the wall to the same Low Tag as the Activators, to open the door.

User talk:Hendricks266

2012-04-10T20:10:05Z

Hank: /* Administrative Requests */

== Administrative Requests ==
Feel free to add requests here if you want a change made to the wiki that is restricted to administrators. Use a level three heading for each issue, like this:

<nowiki>=== Request: ... ===</nowiki>
How about one more 'blank' sub header under Doors, http://wiki.eduke32.com/wiki/Category:Editing_Doors ?

I want to change the title from Locked Doors to Keycard Doors, and make one named Locked Doors to describe various locked/unlock door set ups. Then I think all of Category:Editing Switch Effects http://wiki.eduke32.com/wiki/Category:Editing_Switch_Effects should be integrated to the door section.

Hopefully I posted this right.

Cheers - Hank

Category:Editing Parallaxed Skies

2012-04-04T01:43:50Z

Hank: /* Correctly Parallaxed Skies */

Category:Editing Parallaxed Skies

2012-04-04T01:27:55Z

Hank: /* Correctly Parallaxed Skies */