Region Kill System [v1.5]

Sergeant

Few folks on Europe have been asking me for this, so I decided to just put it up here, so everybody can use it.
Here is the link to download the system. Read the Init trigger for instructions.
** This requires Jass NewGen editor. If you don't have it, download it from the link below **

**UPDATES**

DEBUG == true in the Init trigger allows you to see where your regions are being placed. Set it to false when you release your map!
Now, instead of specifying a complicated # for tightness, you just decide between 0 (Maze of Fantasy-type regions), or 1 (MoRs/MoHs-type regions)
Added support for multiple death terrain types AND MULTIPLE TIGHTNESS for each of those terrain types, read the Init trigger for details.
Improved GoodRegions recognition, but make sure that when you place the GoodRegions, you extend the left + bottom side of each region by one space, while the right + top hug the terrain edge. See this image for an example:

Spoiler:

What is this?

A new form of death triggering. In the past, people either placed regions by hand (a time consuming process), or used terrain kill (a periodic trigger that checks the unit's position every 0.01-0.05 seconds, which, if done with locations, leaks severely).

Why is this good?

If you hate placing death regions, this will rock your boat. Not only does it ensure you don't have to waste time making each death region, and clog up your editor's memory usage by creating several regions, but also it ensures that each region placement is consistent, so people who play your maze will not die from random "noob regions".

Why not just use terrain kill? After all, you did post a "terrain kill with adjustable tighness" trigger...

Terrain kill does use a lot of in-game memory, even with the leaks removed, because it is checking periodically. This system places all the regions at the start of the map, as the game is loading.
But more importantly, the terrain kill is based on checking terrain rectangles, so corners/diagonals appear very tight. I'll let this set of images do the talking:

This is what traditional terrain kill is like, note how the death parts extend out onto the path for corner/diagonals:
Spoiler:
You can use the adjustable-tightness terrain kill, but then apart from the lag issue, to achieve truly good regions with good corners,
you have to set the tightness to such a low value that you'll be able to bug across the death parts:
Spoiler:
Now this is what my region kill system does, by making several tiny regions to maximize the path/offpath distinction, for a far more accurate set of regions:
Spoiler:

What are the current limitations?

You need to use Jass Newgen Editor (which I would heavily recommend anyway, as it lets you test your map in window mode, among other incredible features). You can download it here: http://www.wc3c.net/showthread.php?t=90999

If you have any questions/comments/suggestions/bugs, feel free to go fuck yourself.

Sergeant

Few people were having issues with a bug, so I changed a few things. Should work now. If you downloaded it, get the new ver.

Commander

Id like to have sex with Mrs. Region kill l8er around 6-8pm? sound good uhm saturday?

Sergeant

Updated to support multiple death terrain types, for maps like mor4, moh5, ppf, etc.

Sergeant

wohoo new version! in lieu of the retarded current state of mazing thread, I've decided to change up the options on the region generator.

You have 3 options for the Tightness variable:

Tightness = 0 (Maze of Fantasy, vSex mazes, maze of PPF)
Tightness = 1 (MoH maps, MoR maps, left + bottom sides not buggable)
Tightness = 2 ("Classic mazes" from the "good ol' days of mazing". Essentially terrain kill)

Enjoy

Recruit

I'm not sure if it's possible, but arun, can you make so its random what sides you can go off path and random tightness? (ofc between a min and a max value)

Sergeant

bloodasb wrote:: in the otherone someone made oun of you for being brown and ur about to cry/ poop im not sure

my brown friends and I invented this thing called The Wall Test.
We put our hand next to the wall at a party. If our skin color is darker than the wall, we won't fit in.

Chances are we get fucked 100% of the time.

Derige_JT wrote:: I'm not sure if it's possible, but arun, can you make so its random what sides you can go off path and random tightness? (ofc between a min and a max value)

of course. but i cant think of one practical use for that. aside from just pissing people off

Recruit

I guess i found a bug on this killing system. You can go between the "Areas". Check the image:

Spoiler:

Anyway I'm looking forward to use this system on the map im making : )

Oh, and a doubt about this. I thought about using tightness = 1. U think its appropiate for an skate map ? Remember i dont want loose regions like in PPF ! They are too "soft" xd

Sergeant

GOVO wrote:: I guess i found a bug on this killing system. You can go between the "Areas".

Thanks for pointing that out GOVO, pretty big bug. I'll have to look into a way of fixing that, and I don't have the time at the moment. So in the mean time, just avoid that issue by creating extra regions where the off-path changes, and then just add them to the Death trigger. Shouldn't be too much work.

Heres how:

Spoiler:

And regarding your skating map, it depends on the tileset. If its a 'thin' tile like murloc slide, or ppf first ice levels, use tightness = 1. If its a bigger path like ice on snow (da skate away, itw), use tightness = 0.

Captain

you should just make a simple java interface for this, just imputs and dropdown menus, then this system would take off for all the map noobs( and lazy people like myself )

i can explain if u reply and dont understand im just to lazy right now and hyped up on 5 hour energy and NoS

Recruit

nomorholywar wrote:: of course. but i cant think of one practical use for that. aside from just pissing people off

Well i mean... same everytime but not so its always the same sides are bugable. like in mor :S

Commander

i found some problems with ur region kill system, i dont believe i did it :/
And even when i changed the tightness it didnt matter lol...

Btw. Olo is teal

Region Kill System [v1.5] Arun_110

Sergeant

can you host it when i get on? ill take a look

Sergeant

OK! The system is FINAL. Been totally updated, and works extremely well for diagonals.

Also the DEBUG mode is brilliant. Have fun.

Recruit

Okay, it was working perfectly yesterday, but when I saved today, jasshelper keeps saying:

"Nested scopes cannot have initializers"

I didn't edit the trigger since yesterday.

Here's the trigger:

Spoiler:

Moderator

I havent looked at normors map so i cant tell you

But if it was working and now isnt you mustve changed something, things dont just break mysteriously
Well they do break mysteriously, but theres always a reason

Go back and compare yours to nomors and see what differences there are

Moderator

what you posted isnt a nested scope
its just a scope

for it to be nested, it has to be within something else
i'm guessing you made a function without ending it

ie
function asf takes ... returns ...

(missing endfunction)

anyways what im saying is
the problem might not be in that trigger
or at least in the stub you posted
it'd probably be above it, but i dont really know without seeing the whole thing

Recruit

Works perfectly, Going to use it for my last Mof.

» Need Region kill help
» Region Question
» death regions kill patrols ><
» Hearthstones ranking system vs ELO/MMR
» The Ultimate Sliding System