![]() |
#1 |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() 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:
Other: Please give other suggestions, and please remember, they have to be REALISTIC! Last edited by Anachron : 08-24-2009 at 04:13 PM. |
![]() |
![]() |
Sponsored Links - Login to hide this ad! |
|
![]() |
#2 |
.▲▼▲	
|
![]() RemoveMemoryLeaks()
__________________ |
![]() |
![]() |
![]() |
#3 | |
User
Join Date: Oct 2003
Posts: 150
![]() |
![]() Quote:
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. ) Last edited by Switch33 : 08-19-2009 at 11:14 AM. |
|
![]() |
![]() |
![]() |
#4 |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() 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. |
![]() |
![]() |
![]() |
#5 |
BuranX
|
![]() afaik today 1.24b will be released O_O so...
__________________ |
![]() |
![]() |
![]() |
#6 |
Perfectionist noob
Join Date: Mar 2009
Posts: 255
![]() ![]() |
![]() SetLightningX1(), SetLightningX2(), SetLightningY1(), etc...
__________________GetItemGoldCost() TriggerClearEvents() GetUnitDamage() EVENT_PLAYER_UNIT_DAMAGED And most important: GetPointZ(x, y) |
![]() |
![]() |
![]() |
#7 |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() 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. Last edited by Anachron : 08-19-2009 at 11:48 AM. |
![]() |
![]() |
![]() |
#8 | |
Lackadaisically Absent.
Respected User
|
![]() Quote:
![]() native MoveLightning takes lightning whichBolt, boolean checkVisibility, real x1, real y1, real x2, real y2 returns boolean native MoveLightningEx takes lightning whichBolt, boolean checkVisibility, real x1, real y1, real z1, real x2, real y2, real z2 returns boolean |
|
![]() |
![]() |
![]() |
#9 | |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() Quote:
(Its the same why you don't use BJs at all, aslong as they are bad) |
|
![]() |
![]() |
![]() |
#10 |
Lackadaisically Absent.
Respected User
|
![]() ...
__________________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. Last edited by Pyrogasm : 08-19-2009 at 11:53 AM. |
![]() |
![]() |
![]() |
#11 |
Perfectionist noob
Join Date: Mar 2009
Posts: 255
![]() ![]() |
![]() 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().
__________________ |
![]() |
![]() |
![]() |
#12 | |
Two Blue
|
![]() Quote:
MoveLightningSource(lit,x,y,z) MoveLightningDest(lit,x,y,z) than a function per component... |
|
![]() |
![]() |
![]() |
#13 | |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() Quote:
|
|
![]() |
![]() |
![]() |
#14 | |
.▲▼▲	
|
![]() Quote:
|
|
![]() |
![]() |
![]() |
#15 |
User
Join Date: Mar 2009
Posts: 1,079
![]() ![]() |
![]() Really, be serious. I mean I wish that too, but it could never be possible.
__________________So, any serious things you want to have? |
![]() |
![]() |
![]() |
Thread Tools | Search this Thread |
|
|