[JASS] Jass error:"String literal size limit exceeded /unclosed string"

[Titanhex]

I'm getting this error when I save with JassHelper, and have no idea what it means. It's appearing on line 39819, and I imagine there's a good chance I stretched the total lines farther than they'd go? But I kinda doubt it.

Still the issues pops up in this function:

 //===========================================================================
// Trigger: villagers
//===========================================================================
//TESH.scrollpos=0
//TESH.alwaysfold=0
function Trig_bla_Copy_10_Copy_Conditions takes nothing returns boolean
    if ( not ( GetUnitTypeId(GetTriggerUnit()) == 'ngst' ) ) then
        return false
    endif
    return true
endfunction

function Trig_bla_Copy_10_Copy_Actions takes nothing returns nothing
    call CreateNUnitsAtLoc( 1, 'nvil', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'nvl2', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'nvlw', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'nhef', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'nvlk', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'nvk2', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'h002', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'h003', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
    call CreateNUnitsAtLoc( 1, 'h004', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )
endfunction

The particular line the error is directed at:
call CreateNUnitsAtLoc( 1, 'h003', Player(PLAYER_NEUTRAL_PASSIVE), Location(0, 0), 270.00 )

The trigger is pointed at a villager unit that creates several units to choose from when you click it. The units that you can pick and drop appear on a location nearby.
What does this error indicate?

Some other information that may help:

If I disable the trigger, it just gives the previous trigger before it the same error. So it is likely being created by a previous trigger.

This error ONLY arose when I exported the entirity of triggers from a previous map to a whole new map.
However, if I export the triggers from this version to a similar version, it doesn't have an error. On the other hand, if I export the triggers from this version to an older version with a set of unit clickables that aren't as up to date, it does error.

In terms by version:

VD&D TE => SMW (Works fine)
VD&D TE => Beta 091 (This Error)
VD&D GP => TnZ VDnD (This Error)

Haven't tried GP => SMW or Beta 091, but I imagine it would error since the palettes are different. Will possibly try later.

I couldn't imagine that the strings or coding got damaged between transfers. I imagine it has something to do with what's physically on the map vs what's on the triggers. However, because I don't know what the error code means exactly, I can't be sure.

I don't want to spend 10 hours on this map setting it up only to not be able to fix the error and have to toss the project.

 

[Rui]

The position of the lines does not matter.
But I don't understand, are you using JASS? Or do you convert the triggers to custom text after you finish them? The only possible error I can find in that line is the custom unit with data 'h003' missing, you could have deleted and re-created a unit from another race, which would result in a different rawcode.

By the way, JASS-fixing problems go on the Triggers & Scripts forum with the

[/U] prefix.
[I]~Thread Moved[/I]

 

[Titanhex]

Oh hey, I gotcha. I just remembered this was an important from a newer map to an older back to try to solve a bug and see if I couldn't clear some file size I wasn't using. I don't think this part of the map has been added in this vers. though, so it all makes sense now.

 

[HINDYhat]

This is simply because you forgot to close a string somewhere in the map (double quotes to open/close strings), I think.

 

[Titanhex]

Call me odd, but I have to bump this thread. Gonna update the error, but now I'm getting this error again. Let me explain what I was doing and what I'm doing now.