WE sux

Yes that's right, WE sux and hard. That's why I am probably going to end with it now (and I have almost 2,5 years of practice with it, meh, wasted time). I recommend you to do like me.

Magnetic field appear on one part of my map. Well, I dunno how to call that thing, but that's no matter. Mainly is that my triggers start messing when unit step into that part of map. Or they just don't work.
I was check everything and there's no logical reason for doing that. That part of map is that same as other parts, there's not distinguished pathing or terain or units and I have no special region there. I was try almost everything to fix it, and I am undisposed to made it from start. Besides, where I have safety that this will not appear again?

What I was want to say with this? It's just warning for you. Made mor Back-ups, watch your scripts carefuly or just give it the deep six and spend your time otherwise. I am going to wait for StarCarft2 now, I will steal some WoW models and made some fantasy mod... In C++... WE just sux...

Probably goodbye

(and if anyone know how to fix that bug, plz tell me... I have still little hope in deeps of my heart :)

Actually if that part of your map is upper border... is it?

Magnetic field?? what are you talking about?? At least for me is not clear the bug.

I have no idea what 'magnetic field' means and have never experienced this. Why should I quit like you, because you experienced something strange? Time is not wasted just because something eventually goes wrong, or because it was hard to get where you are, or because it has to end sometime.

If I recall well there was a similar bug in warcraft 2
Spells were not working properly near the upper edge of the map.

This can happen if spells are casted by dummies and can target on points,
then if you use random points your spell target would eventually get off map limits, and it will cause it to fail.

When jass trigger encounters errors like that it simply stops executing
and returns.

So I suggest you double check your spells,
make them print their coordinates on screen...


EDIT:
On the other hand if your magnetic field is in the center of the map
you have passed nulled or somehow invalid location to a spell,
in that cases game simply assumes location is (0,0)

No, it's not near any border of center (or maybe, I dunno how big is that area), I don't use any spells there or any specific triggers... It's not magnetic field, I just call it like that because I dunno how to call it (maybe anomaly?).
I don't send or copy that map and I don't do anything with it outside of WE. It's just stupid bug, damaged file or what... Just lack of WE. It's not only strange, this is something what make map unplayable. I don't care if you quit or not, I just say what WE can do and it's on you if you want risk it. It's warning for you.
This is first time in my life when I see this, I can't explain what does this mean. Some triggers do things what should do other triggers. Some triggers does not work sometimes does not work conditions. It's absolutely messed.

EDITED: I have one trigger what move your unit in period. But this trigger work like others. Until you step into anomaly...

Well universe is a strange place,
sometimes thing just get out of the ordinary...

My advice - make a new map, it will take less time

I start with new map, and when I will be near end then it will crash again...
Well I can copy triggers, I start maybe one day, but I am undisposed now...

... tragic, we lose another person.

Well yes sometimes it is best to let some time pass...

There are plenty of better reasons to say the world editor sucks than "I screwed up and don't know what I did wrong." Programing is filled with these types of problems. It usually turns out you made a typo and just don't see it.

Real reasons WE ain't so great:
- default JASS is a mediocre language
- default JASS parser SUCKS. Crashing because of common errors is UNACCEPTABLE.
- object editor has a ton of "gotchas" (some fields do nothing, some fields don't do what they say, some fields are hidden when they shouldn't be, etc)
- the brush list
- main editor is cpu-intensive
- various things work differently in-game than they do in the editor (give a unit a negative flying height and put it over water; very different results)

I didn't wrong anything. Leastwise from logical way. Well, if is WE unlogical then it's also good reason to quit. I am absolutely 100% sure that this is not my wrong. How I can't be? The strange anomaly apear in part of your map, where is practical nothing. And also nobody can't fix it and map is unplayable becouse that.

Hee hee hee... ohhhh ho ho.

Maybe stat spending previously "wasted" Editor time taking Grammar lessons?

Better yet, perhaps post your map so we can see what the error is. Think a little before whining and quitting.