I'm having trouble with one of my new maps im making... I have already used all 256 switchs! Is there a way to get more switchs to use? Like say, 500?
None.
Just use death counters.Use 0 deaths as cleared and 1 death as set.
Edit: Why would you need more than 255 switches?
None.
So there is no way of getting more switchs? That sucks... how do i do that death thing ur talkin about?
None.
Do you want randomization or just switches?
None.
Arg! dont want randomization, i was just wondering if there is a way to get more than 256 switchs besides recycling... guess not...
None.
Just set deaths of a unit that you don't use in your map. If you set death to zero then it is representing cleared and if you set death to one then it is representing set.
None.
Ok, i will try it............. Siiigh... I wish there were more updates/programs/add-ons out there for SC.... Especailly for my case.
None.
What kind of map takes over 500 switches?
None.
Wow, that you used 256 switches is one thing, but that you think you might need 500 is another.
For one thing, I guessing you have an inefficient system, to need so many. In my experience, the systems that require the most switches, are the ones most benefit from death counters.
If you could give us an example of whats taking up all your switches, we could come up with the best way to minimize the need. As it is, I'm sure you are using way more than you need to. Sorry, I'm not giving you the benefit of the doubt.
None.
Switches are a bad choice, they can't be assigned to player, so you can't use the "current player" to reduce the trigger work. Also there are only 2 volumes for a switch. With a single death counter(DC) you can replace 8-limitless switches depending on the situation. DC is the choice if you know your stuff.
None.
One death counter can also store 31 bits, or switches. IE, 0 means that nothing is on, 1 means "switch" 1 is on, 2 means "switch" 2 is on, 3 means "switch" 1 and 2 are both on, 4 means "switch" 3 is on, etc...
You can probably double that with negative deaths, and multiply that by 8 to give 248 "switches" in one death counter.
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"
whoops, forgot me math...
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"
One death counter can also store 31 bits, or switches. IE, 0 means that nothing is on, 1 means "switch" 1 is on, 2 means "switch" 2 is on, 3 means "switch" 1 and 2 are both on, 4 means "switch" 3 is on, etc...
You can probably double that with negative deaths, and multiply that by 8 to give 248 "switches" in one death counter.
And how do you plan to check or modify them?
Like sw3 is being checked, it might look like this:
DC = 100
DC = 101
DC = 110
DC = 111
And required conditions are being doubled after each "extra switch" -_-.
None.
And how do you plan to check or modify them?
Like sw3 is being checked, it might look like this:
DC = 100
DC = 101
DC = 110
DC = 111
And required conditions are being doubled after each "extra switch" -_-.
For one, you might try binary countoffs, and check the biggest switch first. It requires fancy ordering of triggers, but is entirely possible. You'll note that switch 3 is at least 100 if you don't use more than 3 switches. I can't think of any better way, as any way to get all 31/2 switches would require binary countoffs anyway. That also means you'd need a storage DC, unfortunately. Nobody could possibly use all the death counters and switches anyway, so I can't see someone actually using all 31/2 bits in a single death counter. It's woefully inefficient.
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"
The most I ever use in a map is one switch, lol.
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"