What is wrong with this?

03-28-2007, 08:22 PM

When I launch the WE with the JassNewGen pack and try saving my map it complains that k is not an array in this function at set k[loopIndex] = udg_scoreboard_kills[loopIndex].

JASS:

function GiveAwards takes nothing returns nothing
    local string array p    //players
    local integer array k   //kills
    local integer array d   //deaths
    local integer array n   //nodes
    local integer loopIndex
    local integer loopIndexEnd
    local real score1
    local real score2
    local string winner
   
    ...

    //GET KILLS
    set loopIndex = 1
    loop
        exitwhen loopIndex > loopIndexEnd
        set k[loopIndex] = udg_scoreboard_kills[loopIndex]
        set loopIndex = loopIndex + 1
    endloop

    ...

EDIT: And renaming the variable doesn't even work!!! I changed it to kk but the syntax checker still thinks it is k.

03-28-2007, 10:55 PM	#2
Vexorian	There was a bug like this in an older version of jasshelper and I fixed it, so first make sure you are using the latest one. If updating doesn't work, I'll need the map.

03-30-2007, 07:46 AM

Moss

Arg! Now it says "new is not a member of csmissile". On the last line of this code:

JASS:

function CollisionMissile_Create takes string MissileModelPath, real x, real y, real dirangle, real speed, real AngleSpeed, real MaxDist,  real height, boolean UseNewCaster, real Collision, code OnImpact returns unit
     local timer t
     local integer k
     local trigger R

     local unit m


        set k=cscollisionmissile.create()
     
        if UseNewCaster then
            set m=CreateCaster(dirangle,x,y)
            set k.new=true

I don't know if all this newfangled JASS stuff is worth it.

EDIT: And now I tried going back to WEHelper with JassHelper 9.5.1 which was working fine before this and when I open the map and try to save it again it crashes the editor. Grimoire or whatever did something to it because it saved it even though there were compile errors and now my map is screwed up. This is terrible.

03-30-2007, 01:00 PM	#4
Vexorian	You have to stop using WEHelper... If it is not worth it don't use it, but in advance I will tell you that you did something very wrong , but you should really send me the friging map. 0.9.5.1 is pretty awesomeish old...

03-30-2007, 06:50 PM	#5
Moss	Doh, I remembered why it was crashing with WEHelper, because I had to go pack to the 1.20 version of worldedit. So that is fine, my map isn't lost but I still have the latest syntax error I mentioned when I try to use JassHelper 9.7.3. I have sent you the map.

03-30-2007, 07:44 PM

Vexorian

really, stop using WEHelper.

from the caster system changelog:

 Version 14.3
     CasterSystem:
         - Fixed some issues that may cause errors with newest versions of jasshelper
         - Fixed DamageOnlyVisibles() not preventing to harm units in fog/black mask.
         - Added CollisionMissile_SetTag and CollisionMissile_GetTag

You happen to have caster system 14.2 ...

/ update it, you will eventually have to update anyways because of the changes I am doing to hydra

03-30-2007, 10:34 PM	#7
Moss	OK, so I need to simultaneously update to JassHelper 9.7.3 and CS 14.3. See I tried doing that already before you released 9.7.3 and I got that k>0 error... Well thanks for your help, sorry for bothering you.