Can I remove Limit of 52 custom heros for Gameplay Constants?

I use war3 editor that came with game. I've been working on my map for over a year now always adding more heros and content. just today i have finished making a 53rd hero and it wont let me add that one to my Gameplay Constants list for limiting hero amounts players can pick.

every time i add the 53rd it just erases it from list or whichever happens to be at the most bottom of list, capping it at 52.

how can i get by this?

thx for your time.

what list? Tried keeping shift pressed when editing the list?

The list brash is talking about is:
Techtree - Dependency Equivalents - Hero
in the gameplay constants

and to answer the question, you can't add more than 52 heros to that list. shift doesn't help at all.

you can however make some dummy units and use them as Techtree - Requierments to fake it.

yes, that is what i mean.

what do you mean by using a dummy unit to fake.

do you mean that when someone picks that hero to remove that dummy unit and then they can no longer select more heros of that type until thta dummy unit is restored in map?

would it have to be dummy for each player or could it be one for all? my map is a 10 player map for online coop play.

I just dont want other players to select same hero as some other player has so there are no dupes in my map. i also do not want more than 1 hero period for any one player.

well u can edit those existing hero X) especially those campaign hero

Did you try shift-clicking and adding the rawcode?

there is nothing to shift-click. unless you can shift-click the add button when adding heros to the list

i go to: Advanced > Gameplay Constants> Techtree Dependency Equivalents - Hero

after clicking that, click "Edit button" or double click it directly

Then pick heros to add.

It lets me add it in but when i click okay and then go back and check if it really did remember it, it doesn't.

there should be no limit to this imo.

Highlight Techtree Dependency Equivalents - Hero. Hold down shift and double click on it. Add the raw code of your hero/es. See if it saves them.

i hate to quote myself but...




one dummy per player, though you can of course loop through your players and add/remove one dummy unit at the same time.


i dont really understand what you want but.. tried this?

Player - Limit training of Heroes to 1 for Player 1 (Red)

Please state specifically that you actually tried adding the rawcode to the list (by typing it in, if you have the add/move buttons you're in the wrong place). You didn't seem to understand how to do that.

Ok. Im so sorry if I wasn't being clear enough.
I did try with the regular way of adding units ('click-list') aswell as I tried the 'shift-click-giving-the-rawcode-string' way. None of them accepted more than 52 units.

Well did what you said. I put raw code in but it doesn't hold either.

Post 2:



that has always been there

that is the reason for the gameplay constant i was talking about. that tells the game that my hero is indeed a hero.. one that needs to be "limited"

until i can put it in there that code above is useless.

However, i did try what you said by having a techtree requirement attached to the unit itself looking for a dummy unit requirement and while this does check fine, it still lets me pick more than one hero after i pick him. In other words it lets me pick fine with that restriction.. but whether or not that restriction is in place the altar still does not realize he exists and will let me make another hero of another type.

Edited by Blade.dk. Reason: Merged double posts.

Have _all_ heros require a single dummy unit type named 'only one hero allowed'. give 1 to each player at the start of the map. kill a players unit when a hero is trained.

For allowing more then one hero: Keep an integer array holding the number of heros a player has, and kill the unit when they reach that number. rather simple, really.

Brash, read our rules: http://www.wc3campaigns.net/faq.php?..._revised_rules

Double posting is not allowed - I merged your posts, but next time, please use the edit button instead.