Going back to some old WDE's that I never finished/never started, and ran into a problem for the "Show me how you build" WDE.
Problem
I've got Building A start off with Power Level 1.
Power Level is upgradable. Each upgrade increases the radius a small amount, as well as the Power Level by 1 each time(Level 2 Replaces Level 1, etc)
Building B requires Minimum Power Level 1.
Building C requires Minimum Power Level 2.
If I upgrade to Power Level 2, I can no longer construct Building B.
Test 1
Gave Building A Power Level 1 and 2.
Can only construct Building B within the radius of Level 1.
Building C can be built anywhere within the radius of Level 2/1
Test 2
Gave Building A Power Level 2.
Gave Building B "Require Power Level 1" and "Require Power Level 2"
Cannot build Building B (Removing Require Power Level 1 fixes this, but then cannot be build in Power Level 1)
In the end, I want to be able to build Building B(which needs Minimum Power Level 1) anywhere within the radius of Power Level 5.
Suspicions
Power Source and Power User behaviors share a field Behavior: Power Link. For all intents and purposes, Level 1 User and Level 1 Source both have the same Power Link(PowerLevel1).
I tried adding extras to the field, but it must be typed out manually and I'm not sure if I am doing it right(or if I can even link multiple Power Links)
Tried PowerLevel1,PowerLevel2
tried adding a space after the comma
Also tried leaving it blank, but it wont work
For the Power User behavior, the tooltip for the Power Link field states Types of power sources that will power this behavior, which leads me to believe I CAN specify more than 1 power source for it to function, but might just be a broad generalization.
Anyone have an idea? I really don't feel like doing a hacky method... there's already alot of work just to have a Power Visual show up for each Power Source behavior level.
•Gave Building B "Require Power Level 1" and "Require Power Level 2"
•Cannot build Building B (Removing Require Power Level 1 fixes this, but then cannot be build in Power Level 1)
For the second part, Require Power Level 1 and Require Power Level 2, have you tried using an OR instead of the AND, since the only way this might possibly work is if you had a power level 1 and power level 2 in close vicinity to each other, which is I'm guessing not what you are aiming for. Just a thought.
You cannot "AND" or "OR" power behaviors... At least not that I've been able to.
EDIT: OH jeez, I just got what you meant. It's not an AND, requiring both. It's an AND, as in, I gave it both this AND that. Think of it like a set effect, where you have multiple "effects" in the set. I gave it multiple Power Level Requirements in the field
The power link is just a string that can be used for orthogonal power systems. It could be called blue cheese and still do the same. Power source and user behaviours with the same link interact while those with a different one do not.
I know. I was just pointing out that they Power User and Power Source must both share the same Power Link string to interact. I did some testing, leaving one blank and what not and it didn't work.
Looks like I am going to have to use a hacky method... Or... maybe there's a way of "upgrading" a power source?(As in, not replacing PowerLevel1 with PowerLevel2, but modifying the field through an upgrade) Hmm, I'll take a look now.
EDIT: Ok... the only field modifiable for Power Behaviors(Source or User) is Requirement... so you cannot modify the Radius or Minimum Power Level through upgrades....
EDIT2: Solved! Wow... so damn simple, why didn't I think of it earlier.
So, I have 5 Power Source Behaviors, each with a radius and Minimum Power Level. Level 1 has smallest radius and minimum power level 1, while level 5 has the largest radius and minimum power level 5
5 Power User Behaviors, each requiring a Minimum power level of that level.
Instead of having Power User1 and Power Source1 share the same PowerLink PowerLevel1, and Power User2 and Power Source2 have PowerLevel2 in the PowerLink, I just made ALL User and Source have the SAME PowerLink. I just called it PowerLevel, and all 10 behaviors have the identical PowerLink, and it works perfectly while testing random combinations of what should obviously not work and what should work.
If only I would have cross referenced the Warp Prism's power behavior(I forgot that Prism's also gave off power)... it's Power Link is the same as the Pylon, thus allowing any protoss building to be built inside the Power radius of the Prism.
The wiki doesn't really point to the fact that you can link more than 1 Power User and/or Source to each other. The way I read it, was Each Power Source and Power User needed the same Power Link. Since the Protoss basically get all their Power Source from the Pylon, it's easy to make 1 Power User and give it to every building/warpable, which is how SC2 is setup.
The fact that I overlooked the Warp Prism at first, and how it is setup, lead me to believe that Power Level 1 Source and User had to be together, and Power Level 2 Source and User had to be using their own Power Link, which in fact, I found out you can have multiple Levels connected any which way you really want.
Besides, your Power Lines map, has 1 User and 1 Source that share 1 Level. It wouldn't have enlightened me. Unless of course there's an updated file somewhere in those 14 pages of hundreds of map updates/uploads in that Community Project thread.
Going back to some old WDE's that I never finished/never started, and ran into a problem for the "Show me how you build" WDE.
Problem
Test 1
Test 2
In the end, I want to be able to build Building B(which needs Minimum Power Level 1) anywhere within the radius of Power Level 5.
Suspicions
Anyone have an idea? I really don't feel like doing a hacky method... there's already alot of work just to have a Power Visual show up for each Power Source behavior level.
Thanks for any input!
Regarding:
Test 2
•Gave Building A Power Level 2.
•Gave Building B "Require Power Level 1" and "Require Power Level 2"
•Cannot build Building B (Removing Require Power Level 1 fixes this, but then cannot be build in Power Level 1)
For the second part, Require Power Level 1 and Require Power Level 2, have you tried using an OR instead of the AND, since the only way this might possibly work is if you had a power level 1 and power level 2 in close vicinity to each other, which is I'm guessing not what you are aiming for. Just a thought.
@Deadzergling: Go
You cannot "AND" or "OR" power behaviors... At least not that I've been able to.
EDIT: OH jeez, I just got what you meant. It's not an AND, requiring both. It's an AND, as in, I gave it both this AND that. Think of it like a set effect, where you have multiple "effects" in the set. I gave it multiple Power Level Requirements in the field
The power link is just a string that can be used for orthogonal power systems. It could be called blue cheese and still do the same. Power source and user behaviours with the same link interact while those with a different one do not.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
@DrSuperEvil: Go
I know. I was just pointing out that they Power User and Power Source must both share the same Power Link string to interact. I did some testing, leaving one blank and what not and it didn't work.
Looks like I am going to have to use a hacky method... Or... maybe there's a way of "upgrading" a power source?(As in, not replacing PowerLevel1 with PowerLevel2, but modifying the field through an upgrade) Hmm, I'll take a look now.
EDIT: Ok... the only field modifiable for Power Behaviors(Source or User) is Requirement... so you cannot modify the Radius or Minimum Power Level through upgrades....
EDIT2: Solved! Wow... so damn simple, why didn't I think of it earlier.
So, I have 5 Power Source Behaviors, each with a radius and Minimum Power Level. Level 1 has smallest radius and minimum power level 1, while level 5 has the largest radius and minimum power level 5
5 Power User Behaviors, each requiring a Minimum power level of that level.
Instead of having Power User1 and Power Source1 share the same PowerLink PowerLevel1, and Power User2 and Power Source2 have PowerLevel2 in the PowerLink, I just made ALL User and Source have the SAME PowerLink. I just called it PowerLevel, and all 10 behaviors have the identical PowerLink, and it works perfectly while testing random combinations of what should obviously not work and what should work.
If only I would have cross referenced the Warp Prism's power behavior(I forgot that Prism's also gave off power)... it's Power Link is the same as the Pylon, thus allowing any protoss building to be built inside the Power radius of the Prism.
You could have also looked at my power network map or read the wiki.
Contribute to the wiki (Wiki button at top of page) Considered easy altering of the unit textures?
https://www.sc2mapster.com/forums/resources/tutorials/179654-data-actor-events-message-texture-select-by-id
https://media.forgecdn.net/attachments/187/40/Screenshot2011-04-17_09_16_21.jpg
The wiki doesn't really point to the fact that you can link more than 1 Power User and/or Source to each other. The way I read it, was Each Power Source and Power User needed the same Power Link. Since the Protoss basically get all their Power Source from the Pylon, it's easy to make 1 Power User and give it to every building/warpable, which is how SC2 is setup.
The fact that I overlooked the Warp Prism at first, and how it is setup, lead me to believe that Power Level 1 Source and User had to be together, and Power Level 2 Source and User had to be using their own Power Link, which in fact, I found out you can have multiple Levels connected any which way you really want.
Besides, your Power Lines map, has 1 User and 1 Source that share 1 Level. It wouldn't have enlightened me. Unless of course there's an updated file somewhere in those 14 pages of hundreds of map updates/uploads in that Community Project thread.