What to change on Wc3

Hello all. Since the new Patch (1.24) has been released, I think its time
to ask for other fixes.

I am collecting a list of signatures to get blizzard to change their code,
here are some suggestions I made:

• Camera
  1. SetCameraTargetPositionX
  2. SetCameraTargetPositionY
  3. SetCameraTargetPositionZ
  4. SetCameraEyePositionX
  5. SetCameraEyePositionY
  6. SetCameraEyePositionZ
• Arrays
  1. Index > 8191
  2. 2D Arrays
  3. Assoziative Indexing
• Items
  1. GetItemGoldCost()
• Trackables
  1. add GetTriggerPlayer()
  2. add RemoveTrackable()
  3. add MoveTrackable()
• Lightning
  1. SetLightningX1()
  2. SetLightningX2()
  3. SetLightningY1()
  4. SetLightningY2()
• Events
  1. TriggerClearEvents()
  2. EVENT_PLAYER_UNIT_DAMAGED
  3. GetUnitDamage()
• Location / Coordinates
  1. GetPointZ()
• Heroes
  1. More then 5 Hero Skills possible
• Minimap
  1. HideMiniMap()
  2. SetMiniMap(PATH)
  3. DisableCameraReset()
• Information
  1. about SetUnitLoc()
  2. about the "return-bug"

Other:

• 
  Object Editor Functions

Please give other suggestions, and please remember, they have to be REALISTIC!

RemoveMemoryLeaks()

Wow pure realism. . .



How bout fix hashtable problems? Since they didn't even get that right.

Also. . . it's sort of funny how some maps suddenly don't work that use GUI since the way it was coded was changed.(On blizzard noticing this happened. They will be probably more reluctant to change stuff too much as it may change coding and break mapz like they already did. )

Memory leaks can not be cleaned, since you don't know if you need the data or not.

Its good that I didn't use Hashtables, I knew blizzard would create bugs there aswell.

afaik today 1.24b will be released O_O so...

SetLightningX1(), SetLightningX2(), SetLightningY1(), etc...
GetItemGoldCost()
TriggerClearEvents()
GetUnitDamage()
EVENT_PLAYER_UNIT_DAMAGED

And most important:
GetPointZ(x, y)

They surely will NOT fix the Trackables, also there are many other things mappers want.

Edit: That was for Toadcops post.

I updated the list.

What's wrong with those?

They call to much actions.
(Its the same why you don't use BJs at all, aslong as they are bad)

...

That's retarded. Why don't we want a MoveLocationX() or MoveLocationY(), then? Why not break up every function so that we can have every permutation of the possible arguments just for the sake of some arbitrary 'faster'?

Hell, I've never even heard of anyone complaining about MoveLightningEx() being too slow.

Ever.

The problem with MoveLightningEx() is that you have to know the old position of the lightning when only one coordinate has to change. Same problem with SetLightningColor().

That would be better solved with:

MoveLightningSource(lit,x,y,z)
MoveLightningDest(lit,x,y,z)

than a function per component...

Hmm, but whats so bad about having one native to change some handle value?

It uses magic.

Really, be serious. I mean I wish that too, but it could never be possible.
So, any serious things you want to have?