1. Updated Resource Submission Rules: All model & skin resource submissions must now include an in-game screenshot. This is to help speed up the moderation process and to show how the model and/or texture looks like from the in-game camera.
    Dismiss Notice
  2. DID YOU KNOW - That you can unlock new rank icons by posting on the forums or winning contests? Click here to customize your rank or read our User Rank Policy to see a list of ranks that you can unlock. Have you won a contest and still havn't received your rank award? Then please contact the administration.
    Dismiss Notice
  3. The Lich King demands your service! We've reached the 19th edition of the Icon Contest. Come along and make some chilling servants for the one true king.
    Dismiss Notice
  4. The 4th SFX Contest has started. Be sure to participate and have a fun factor in it.
    Dismiss Notice
  5. The poll for the 21st Terraining Contest is LIVE. Be sure to check out the entries and vote for one.
    Dismiss Notice
  6. The results are out! Check them out.
    Dismiss Notice
  7. Don’t forget to sign up for the Hive Cup. There’s a 555 EUR prize pool. Sign up now!
    Dismiss Notice
  8. The Hive Workshop Cup contest results have been announced! See the maps that'll be featured in the Hive Workshop Cup tournament!
    Dismiss Notice
  9. Check out the Staff job openings thread.
    Dismiss Notice
Dismiss Notice
60,000 passwords have been reset on July 8, 2019. If you cannot login, read this.

WIP: Maze Making.

Discussion in '"Graveyard"' started by HeretoDLstuff, Aug 19, 2007.

  1. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    Another Tutorial on
    Maze Making

    1) Terrain types and use.

    Some terrain types are thinner, some are thicker.
    mazemaking01.jpg

    Thinner terrain types are harder to work with, thicker ones are easier; let's say we want a thicker one.
    Look at this picture as an example:
    mazemaking02.jpg

    The grass is thick up and down, but diagonally, it's thin. The marble is thick up and down, but CAN'T go corner-wise. Rock tiles are always thin.

    Now look at this example:
    mazemaking03.jpg
    By using marble the tile is thick diagonally, unlike most others.

    Before you decide which to use, consider this: WHY does the type of terrain kill you when you step on it?? In most mazes, grass is the tile that kills. WHY??? Grass in real life can be stepped on!!

    Either make a storyline for it (The sorcerer put a curse on all the grass!) or make it a tile like lava:
    mazemaking04.jpg
    Which would, of course, kill you.

    2) Triggers.

    There are 2 ways to make terrain kill units.
    This is the preferred method:
    • Lava Kills
      • Events
        • Time - Every .20 seconds of game time
      • Conditions
      • Actions
        • Custom script: set bj_wantDestroyGroup = true
        • Unit Group - Pick Every Unit in (Units in (Playable Map Area)) matching ((Unit-Type of (Matching Unit)) Equal to Maze Walker) and do actions
          • Loop - Actions
            • Set TempPoint = (Position of (Picked Unit))
            • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
              • If - Conditions
                • (Terrain type at TempPoint) Equal to Dungeon - Lava
              • Then - Actions
                • Unit - Kill (Picked Unit)
              • Else - Actions
            • Custom script: call RemoveLocation( udg_TempPoint )

    All this trigger does is check every 0.50 seconds to see if the terrain the maze walker is upon is lava. If it is, the unit will be instantly killed. Just copy this trigger for every player, and for every terrain type if you have more than one.

    The other way, after you make the paths, put regions around all the edges. Then for every region, create a trigger like this:
    • Enters
      • Events
        • Unit - A unit enters Region blah blah blah...<gen>
      • Conditions
        • ((Triggering unit) belongs to an ally of Player 1 (Red)) Equal to True [[this is so patrolling units that kill you don’t get killed too]]
      • Actions
        • Unit - Explode (Triggering unit)



    Which one should you use? For thin paths, regions are technically better, because with thin ones, you can walk off the path for a bit and not die if you use the other way. But if you have a very winding path:
    mazemaking05.jpg
    then you will have to make thousands of triggers for every little region, and if you’re making a big maze too, it would take a verly long time to do and could easily be really boring, hard, and it might be better just to use the other way to make it so players can go off the path a TINY SMALL LITTLE BIT: that’s hardly noticeable.

    However, if your paths are long and simple:
    mazemaking06.jpg
    Regions shouldn't matter much in a maze like this.

    3) Patrolling Units.

    For patrolling units, give them a permanent immolation that deals 9999999 damage, and set the AOE to whatever you want, and give the unit locust. There is 2 ways to make them patrol. One way, they star at one place, walk to the end, and then wrap back and start walking again. The other way, they just normally patrol. For normally patrolling, you just do this:
    • Patrol
      • Events
        • Time - Elapsed game time is 1.00 seconds
      • Conditions
      • Actions
        • Unit - Order Maze Patroler 0007 <gen> to Patrol To (Center of (Region blah blah))


    For the other one, do the parts:
    • Part 1
      • Events
        • Map initialization
      • Conditions
      • Actions
        • Unit - Create 1 Evil Dude for Player 6 (Orange) at (Center of Region 000 <gen>) facing Default building facing degrees

    [for making him start]

    • Part 2
      • Events
        • Unit - A unit enters Region 000 <gen>
      • Conditions
      • Actions
        • Unit - Order (Entering unit) to Move To (Center of Region 001 <gen>)


    • Part 3
      • Events
        • Unit - A unit enters Region 001 <gen>
      • Conditions
      • Actions
        • Unit - Move (Triggering unit) instantly to (Center of Region 000 <gen>)
        • Special Effect - Create a special effect attached to the foot of (Triggering unit) using Abilities\Spells\Human\MassTeleport\MassTeleportTarget.mdl



    4) Levels part one: Reviving.

    After each level, if the maze is hard enough, some of your allies might have gotten killed, or even you. If one of your teammates reach the end, however, then you should come back alive. The easy way to do this (and the smart way, I see no reason not to do it this way), is to make your maze walkers heroes, and the use this trigger to revive them:
    • Revive Level Two
      • Events
        • Unit - A unit enters Region Level 2 <gen>
      • Conditions
      • Actions
        • Unit Group - Pick every unit in (Units of type waze walkers) and do (Actions)
          • Loop - Actions
            • Hero - Instantly revive (Picked unit) at (Center of (Level 2)), Hide revival graphics

    Also, you might find this a helpfuly thing to look at for maze makeing.

    5) Levels part two.

    A good mave wont just be paths to walk on, patroling units, and mortar teams bombing the path. The maze of sliding koopas, is a mave map with good ideas that might get you thinking.

    If youre maze is muti player, you can take advatage of that and make things that require two or more people to finish the maze. If youre useing the "terrian type kills" trigger instead of regions, you can change the path in-game. At one point, make the path me blocked off by the terrian that kills. Then make it so if one player stays in a region, the path turns to not killing, but if he leaves the region the path turns back. That way, it takes two players: One to go across, one to make the path clear.

    Use this to make the path turn walkible:
    • Walk through
      • Events
        • Unit - A unit enters (youre region) <gen>
      • Conditions
      • Actions
        • Environment - Change terrain type at (Center of (your region) <gen>) to (the terrian type that doesnt kill) using variation -1 in an area of size 1 and shape Circle


    And use this so when he leaves, the terrian goes back to killing-type:

    • Close again
      • Events
        • Unit - A unit leaves (youre region) <gen>
      • Conditions
      • Actions
        • Environment - Change terrain type at (Center of (Youre Region) to (killing type again) using variation -1 in an area of size 1 and shape Circle


    Credits too:
    Purplepoot - Fixed my terrian kills trigger.
    rageingspeedhorn - I linked to a maze tut of his.
    Parrothead - Some suggestions, and he seems to acually like it, witch made me want to work on it more.

    This is a WIP, if you could give ideas, point out errors, trigger leaks,grammar\spelling mistakes, or suggest anything else to change or add I would like it alot.

    ALSO, ANY TOPICS YOU WANT ME TO ADD TO THIS THAT MOST TUTORIALS DON'T HAVE, TELL ME!
     
    Last edited: Sep 11, 2007
  2. ragingspeedhorn

    ragingspeedhorn

    Joined:
    Apr 30, 2005
    Messages:
    6,521
    Resources:
    14
    Icons:
    5
    Maps:
    7
    Tutorials:
    2
    Resources:
    14
    There are tons of spelling mistakes, one of them being "witch", it is which. Also words such as can't you spell cant and by you spell bye. There are many more which you should be able to find yourself if you read through the tutorial once again.

    Also your first trigger leaks a lot and is not very effective.
     
  3. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    I know.....

    If you could tell me a not leaking one to but there unstead, I would like it..

    EDIT: I am aware I suck at spelling, pointing them out more spificly would help more.

    Thanks for the feedback btw.
     
  4. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    Your first trigger should pick every maze walker and check their position, to

    A) use 1 trigger instead of (no. of players)
    B) be easier to deleak
    C) be neater

    *specifically.

    But just use a spellcheck in general, and then review it for misspellings that are still words.

    Also, in my experience, the art doesn't matter, since the tiles are stored on a grid, and no matter how they look the tiles are always the same size. (like those diagonal tiles in marble: they don't actually connect (except at the corner, and only the corner (where the two corners touch)), they just appear to - the marble actually connects just as much)

    Next, make use of Patrol. (as you did in the first trigger; the second one is thus useless)

    Next, please seperate each trigger into a seperate tag.

    Oh, also, in wc3, I suggest abandoning realism. If grass was touching lava, it would light on fire. If you were that close to lava, you would die. Also, why would you have to run down a path and avoid random units that would kill you for no apparent reason in reality?

    Oh, and you can skip parts of the path with a .5 second interval. I recommend .25 at the absolute most.
     
  5. Parrothead

    Parrothead

    Joined:
    Jun 10, 2007
    Messages:
    778
    Resources:
    10
    Maps:
    8
    Tutorials:
    2
    Resources:
    10
    Why dont you add a way to revive all the heroes when a new level started. It would be helpfull to people that let people choose there maze player. also add to the way you can die, like if someone uses a mortor and someone gets hit by the bullet.
     
  6. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    Ok, thanks.

    I did spellcheck, but not for misspellings that are still words.

    Maybe, but people playing the map might think that they cant go there.

    Acually, Ive had tons of people ask how to do the second trigger....I dont know why, but apperently some really good maze map did it like that in some parts...its more like a seperate thing appart from patroling, not another way.

    K.

    Yeah, I know...lol...I just ment for generaly storyline purposes.

    At the most, or the least? o_O But ok.

    OK, will do.
     
  7. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    That's for 3+ locations to walk to, so you should mention not to do that for back-and-forth.

    Most as in highest interval
     
  8. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    Ok.

    And how would I make it check ALL of the maze walkers terrain in one trigger? Like this:
    • Lava Kills
      • Events
        • Time - Every 0.50 seconds of game time
      • Conditions
        • (Terrain type at (Position of Maze Walker: Fire Fighter 0002 <gen>)) Equal to Dungeon - Lava
      • Actions
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Terrain type at (Position of Maze Walker: Fire Fighter 0002 <gen>)) Equal to Dungeon - Lava
          • Then - Actions
            • Unit - Explode Maze Walker: Fire Fighter 0002 <gen>
          • Else - Actions
            • Do nothing


    Ecept with more if/than/elses to check the rest?
     
  9. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    • Lava Kills
      • Events
        • Time - Every .20 seconds of game time
      • Conditions
      • Actions
        • Custom script: set bj_wantDestroyGroup = true
        • Unit Group - Pick Every Unit in (Units in (Playable Map Area)) matching ((Unit-Type of (Matching Unit)) Equal to Maze Walker) and do actions
          • Loop - Actions
            • Set TempPoint = (Position of (Picked Unit))
            • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
              • If - Conditions
                • (Terrain type at TempPoint) Equal to Dungeon - Lava
              • Then - Actions
                • Unit - Kill (Picked Unit)
              • Else - Actions
            • Custom script: call RemoveLocation( udg_TempPoint )
     
  10. ragingspeedhorn

    ragingspeedhorn

    Joined:
    Apr 30, 2005
    Messages:
    6,521
    Resources:
    14
    Icons:
    5
    Maps:
    7
    Tutorials:
    2
    Resources:
    14
  11. Parrothead

    Parrothead

    Joined:
    Jun 10, 2007
    Messages:
    778
    Resources:
    10
    Maps:
    8
    Tutorials:
    2
    Resources:
    10
    This tutorial is usefull for mazing. I sugest adding more things to it such as how you will die if you touch another unit and such. Maybe add to what the people in the above post said.
     
  12. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    I completle forgot about this, becaus I had to work on a map for a compition! I added most things people suggested, what ones were you talking about?


    |
    v
    Although I havnt added "and such".
     
  13. Parrothead

    Parrothead

    Joined:
    Jun 10, 2007
    Messages:
    778
    Resources:
    10
    Maps:
    8
    Tutorials:
    2
    Resources:
    10
    I was saying put what purplepoot made in the tut.
     
  14. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    Add in some points as to originality in mazes, and some ideas that show how a maze may be funner from a new twist.

    It's always nice to see things (both aesthetic and gameplay wise) that make a maze unique, and I find that can be a deciding factor in the enjoyment of that maze; is it just another maze clone, or is it a new experience?
     
  15. Anachron

    Anachron

    Joined:
    Sep 9, 2007
    Messages:
    6,167
    Resources:
    66
    Icons:
    49
    Packs:
    2
    Tools:
    1
    Maps:
    3
    Spells:
    9
    Tutorials:
    1
    JASS:
    1
    Resources:
    66
    • Else - Actions
    • Do nothing

    Freaking imba action! Lol!

    Btw, why not saving them into a variable and check player slot status and controller? I know its only a tut, but you may add that too! ( prevents memory space )

    And btw, you should add slide aswell! :grin:
     
  16. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    Are there any plans on development?
     
  17. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    If I can think of anything to add\remember what I was going to do, yes!
     
  18. ragingspeedhorn

    ragingspeedhorn

    Joined:
    Apr 30, 2005
    Messages:
    6,521
    Resources:
    14
    Icons:
    5
    Maps:
    7
    Tutorials:
    2
    Resources:
    14
    Currently this tutorial is far from approvable. You need to fix up most of it.
     
  19. PurplePoot

    PurplePoot

    Joined:
    Dec 14, 2005
    Messages:
    11,161
    Resources:
    3
    Maps:
    1
    Spells:
    1
    Tutorials:
    1
    Resources:
    3
    Which is why I asked that, raging.
     
  20. HeretoDLstuff

    HeretoDLstuff

    Joined:
    Feb 27, 2007
    Messages:
    2,093
    Resources:
    4
    Models:
    3
    Maps:
    1
    Resources:
    4
    Well, go ahead and suggest things I need to do....I havnt found time to wrok on it lately, but anything you suggest ill try!