Farm Survival 0.9i

[Moderator]

Date: 17:24:08 25-Jul-12
Map Moderator: -Kobas-
Map Status: Rejected 1/5
Contact map moderator: Visitor Message / Private Message!

Rejection Reasons:
Map has poor or no description!
Map has low quality terrain!

Useful Links:
The Important Site Rules.
You can use Map Development Section for testing and improving your maps.
Need help with triggers/memory leaks? Make a thread in the Triggers & Scripts Section.
Got any World Editor related questions? Make a thread in the World Editor Help Zone Section.
Got any Requests (Terrain, resources, spells, systems, loading screens...)? Make a thread in the Requests Section.
The Important Site Tutorials.
If you have any complaints or questions about your map, please make a thread here:Map Resource Moderation.

Comment: Map must have nice presentation. Please improve terrain.

 

[yumyum]

Version 0.9i = Bug fixes
Version 0.9h = Quick fix for pig and wood
Version 0.9g = Animals have more HP, Fixed Memory Lag at waves spawning (I hope)
Version 0.9f = Add Pig, Animals are more expensive but more effective for less lag, New Plant
Version 0.9e = 5 New Waves, Some extras
Version 0.9d = New Tower, Wooden Wall upgrades
Version 0.9c = 5 New Waves, Animal Armor fix, Some tiny bugs
Version 0.9b = Quick fix for Corn
Version 0.9a = Uploaded

 

[Vengeancekael]

Make the right and lower lanes a bit shorter, to make it a bit more symmetric.
You could also add corns, cattails, flowers, rocks, shrubs, etc. all around the map to make it look more realistic. (These doodads can all be found under Doodad Palette-Environment)
I'd suggest this terraining tutorial to get started: Advanced Terraining Tutorial ^{(by Blood Raven)}

The triggers Start Gold and Lumber, Wave Starter, How To Play, Easy Info, Medium Info, Hard Info, Insane Info, Extreme Info, Unreal Info, Hero Spawn, Light Area and Restart Attack Move Trigger can be merged.
Remove Map Initialization from the wave triggers, since you're running the triggers and ignoring conditions+events.
A lot of your triggers leak, mostly point leaks:
In order to remove them, you need to store the location at which you want to do something (create a unit, move a unit, etc.) in a Point variable, then use the variable in the action and after the trigger, use a custom script which will "clean" the variable and thus get rid of the memory leak.
(Also quick explanation of memory leaks, they're basically created once you specify a point, once you create a unit group, etc. and a high amount of them will slow down the game)
Here's an example:
This trigger leaks:

Hidden

• Wave 1
  • Events
    • Map initialization
  • Conditions
  • Actions
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at (Center of Unit Spawn Norden <gen>) facing (Position of (Triggering unit))
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at (Center of Unit Spawn Osten <gen>) facing (Position of (Triggering unit))
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at (Center of Unit Spawn Suden <gen>) facing (Position of (Triggering unit))
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at (Center of Unit Spawn Westen <gen>) facing (Position of (Triggering unit))

Here's the fixed trigger:

Hidden

(Download your map with the below trigger in it)

• Wave 1
  • Events
    • Map initialization
  • Conditions
  • Actions
    • -------- Here you store the location at which the unit is supposed to be created in a point variable. --------
    • Set Point[0] = (Center of Unit Spawn Norden <gen>)
    • -------- Then you choose the variable as the location in the below action. --------
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at Point[0] facing (Position of (Triggering unit))
    • -------- In this case you have to set the point variable everytime since the location changes. --------
    • Set Point[0] = (Center of Unit Spawn Osten <gen>)
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at Point[0] facing (Position of (Triggering unit))
    • Set Point[0] = (Center of Unit Spawn Suden <gen>)
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at Point[0] facing (Position of (Triggering unit))
    • Set Point[0] = (Center of Unit Spawn Westen <gen>)
    • Unit - Create 10 Mutant Baby Fish 1 for Neutral Hostile at Point[0] facing (Position of (Triggering unit))
    • -------- Finally, you just have to put this custom script at the end of it which will destroy the memory leak. --------
    • Custom script: call RemoveLocation(udg_Point[0])

You'd have to do this everytime you're specifying a location, which means you need to this in a lot of your other triggers.
Also we're not done yet, as you can see, there's another location in the Unit Creation action, "facing (Position of (Triggering Unit))".
To also remove that memory leak, you need to create the variable Point again, but with the array [1], so that it doesn't override the other location.
And you will also have to cnp the custom script and change the [0] part to [1].
Also just so you know, that facing part doesn't make sense, you can't use "triggering unit", when no other unit comes up before that action.

By the way, in order to create a variable, you need to click this button:

You can check out this tutorial if you need more info: Basic Memory Leaks ^{(by Ralle)}

 

[yumyum]

Thank you for you post i'm going to fix it!