[Update] Pro Opinions: Swarm Hosts and Hellbats | swarm host – Vietnamnhanvan

swarm host: นี่คือโพสต์ที่เกี่ยวข้องกับหัวข้อนี้

Pro Opinions: Swarm Hosts and Hellbats

Text by

TL Strategy

Graphics by

shiroiusagi

Pro Opinions: The Swarm Host Problem
(Or Lack Thereof?)

Thanks to Stephano and a few highly visible Swarm Host

Zerg

  • Spore Crawler damage decreased from 15 + 30 vs biological to 15 + 10 vs biological
  • Hydralisk damage against air increased from 12 to 12 + 4 vs biological

Terran

  • Removed Transformation Servos upgrade
  • Changed Hellion/Hellbat transform requirement to Armory

TeamLiquid asked Zerg pros from across all three WCS regions their thoughts on Blizzard’s proposed changes.

Note: We talked to the players the release of the test map, but Blizzard had released their proposed changes.

Note 2: Maybe there’s a Terran questionnaire coming soon.

Do you think there is a problem with Swarm Hosts in ZvZ?

[image loading] Liquid`Snute: Yes, players can turtle up on one base to force a draw like we’ve seen in a few broadcasted matches now. The games last for 2 hours and it doesn’t weigh heavily enough if a player is far ahead in economy. The Spore/Viper/SH/Infestor combination is too strong for its cost. Swarm Hosts are not overpowered in the midgame, but in the endgame they’re way too strong compared to more expensive-per-supply units such as Brood Lords, Corruptors, Banelings and Infestors.

[image loading] Liquid`TLO: I haven’t played any game yet where it became a problem, usually whenever someone went for Swarm Host he was either so far ahead that he would have won with another strategy as well or died in the transition.

[image loading] Acer.Nerchio: There is definitely a problem with Swarm Host in ZvZ because there is no counter play to it right now. It’s not that hard to get to that composition and it’s almost unbeatable because air switch takes too long for the player that is in the economic lead versus the Swarm Host player and he can easily prepare for that (just look at how long it takes to make Brood Lords) with spore+viper. You can try attacking in multiple places but higher amount of queens or spores that kill drops will easily negate that, so if there is a Swarm Host player with experience the games will drag on forever every time.

There should be also a better way to detect burrowed units since overseers die so fast to spores and then there is no way to kill Swarm Hosts. Adding the fact that Swarm Hosts players always make a lot of spores and queens to transfuse makes breaking the camping player almost impossible.

[image loading] coL.Hendralisk: On NA ladder, which is where I play the vast majority of my games, it’s not really an issue. But watching streams, I have noticed people going for a SH style on EU server where the game drags out to a stalemate with obscene numbers of locusts everywhere. Some suggested changes like viper/brood/spore changes will help alleviate this.

[image loading] Roccat_HyuN: I think they’re fine.

Those kind of games don’t happen for me. I played Stephano on ladder; when I have the advantage, all I have to do is match his Swarm Hosts with my own Swarm Hosts and overwhelm him with my resource/numbers advantage to win. You can’t go Swarm Hosts in an even situation — without going for mutas first, you can’t go for Swarm Hosts. Also, it’s possible to just counter them with one big roach-bane attack. I don’t understand the problem.

[image loading] CJ_Hydra: I don’t think there is a problem.

[image loading] SKT_soO: No problem.

[image loading] AX.Impact: Not in particular.

Yes, players can turtle up on one base to force a draw like we’ve seen in a few broadcasted matches now. The games last for 2 hours and it doesn’t weigh heavily enough if a player is far ahead in economy. The Spore/Viper/SH/Infestor combination is too strong for its cost. Swarm Hosts are not overpowered in the midgame, but in the endgame they’re way too strong compared to more expensive-per-supply units such as Brood Lords, Corruptors, Banelings and Infestors.I haven’t played any game yet where it became a problem, usually whenever someone went for Swarm Host he was either so far ahead that he would have won with another strategy as well or died in the transition.There is definitely a problem with Swarm Host in ZvZ because there is no counter play to it right now. It’s not that hard to get to that composition and it’s almost unbeatable because air switch takes too long for the player that is in the economic lead versus the Swarm Host player and he can easily prepare for that (just look at how long it takes to make Brood Lords) with spore+viper. You can try attacking in multiple places but higher amount of queens or spores that kill drops will easily negate that, so if there is a Swarm Host player with experience the games will drag on forever every time.There should be also a better way to detect burrowed units since overseers die so fast to spores and then there is no way to kill Swarm Hosts. Adding the fact that Swarm Hosts players always make a lot of spores and queens to transfuse makes breaking the camping player almost impossible.On NA ladder, which is where I play the vast majority of my games, it’s not really an issue. But watching streams, I have noticed people going for a SH style on EU server where the game drags out to a stalemate with obscene numbers of locusts everywhere. Some suggested changes like viper/brood/spore changes will help alleviate this.I think they’re fine.Those kind of games don’t happen for me. I played Stephano on ladder; when I have the advantage, all I have to do is match his Swarm Hosts with my own Swarm Hosts and overwhelm him with my resource/numbers advantage to win. You can’t go Swarm Hosts in an even situation — without going for mutas first, you can’t go for Swarm Hosts. Also, it’s possible to just counter them with one big roach-bane attack. I don’t understand the problem.I don’t think there is a problem.No problem.Not in particular.

What do you think of Blizzard’s proposed change to hydralisks and spore crawlers? Are there any other changes that you would like to see?

[image loading] Liquid`Snute: This will only change the ZvZ midgame and do nothing to prevent SH stalemates. I don’t know why they proposed this change, it’s not good for anything related to SH. At best, a game here and there that would’ve been a 2-hour SH game will be averted because of the more volatile midgame. But that’s not a fix to the actual problem. The current Hydralisks and Spores are fine as they are. Attention should be directed towards granting Zerg a way to defeat Spore/Viper/SH/Infestor with a more expensive army. Making the Brood Lord immune to abduct would solve the problem without messing with the other match-ups. I hope the developers will give this option a chance.

[image loading] Liquid`TLO: I don’t like those changes that much, they don’t seem that necessary. I’m pretty okay with how ZvZ is at the moment so I can’t think of any good changes to be honest. The turtle style we’ve seen a bunch of time hasn’t happened to me yet, so maybe that’s why!

[image loading] Acer.Nerchio: It’s a very small change which would probably leave Swarm Hosts in ZvZ close to unaffected. Brood Lords would be more viable but in the late game I still think they would not work against mass spores and vipers + queens for transfuse. You need to push with your Brood Lords so you will get abducted every time anyway and you can’t really break the Swarm Host line in a reasonable amount of time with Brood Lords. I think mutas could work much better in ZvZ from this point so we would see Swarm Hosts less but I am not sure it would fix the problem since you can start from infestors or something else and then transition to Swarm Hosts. Mass muta play would be viable but it would be still risky and that’s not what you aim for in competitive play. You want to have a consistent way to beat a strategy.

[image loading] coL.Hendralisk: I think with the changes, mutas might become popular in ZvZ again, since roaches are superior right now and reign supreme. It could be worth testing out to see the effects, seems like an interesting idea.

[image loading] Roccat_HyuN: Rather than looking at Swarm Hosts, I think it would be better if they tweaked Infestors. Right now the range on fungal growth is 10, but I think it would be okay to decrease the range a little and give back its bonus damage vs. armor. Fungal becoming weak is the reason that all we’re seeing in ZvZ nowadays is all-roach fights.

[image loading] CJ_Hydra: In the end, I don’t think Blizzard’s suggested fixes can change Swarm Host vs Swarm Host. If one player goes SH’s and the other player goes SH’s in response, having a long, stalemated game is inevitable. It’s just like in Brood War TvT, where if one player hunkers down with the intent of going for a long game, then you have no choice in following him along. I don’t think a change is needed.

It seems like the fix is aimed at Stephano’s recent games. But if you look at Korean leagues where the highest level of competition is at, it’s hard to find those kind of SH games because Zerg players play a very tight game and are quick to notice tech switches. If Stephano played Korean players, I don’t think he’d be able to play that type of game. I don’t think ZvZ needs any kind of patch.

[image loading] SKT_soO: If you make mutas easier to use, you’ll see more Swarm Host use. It seems like where would be less roach vs roach games , and more muta vs muta ,or muta vs Swarm Host games.

[image loading] AX.Impact: There are barely any games where you see Swarm Host vs. Swarm Host. There’s nothing I want changed in particular.

This will only change the ZvZ midgame and do nothing to prevent SH stalemates. I don’t know why they proposed this change, it’s not good for anything related to SH. At best, a game here and there that would’ve been a 2-hour SH game will be averted because of the more volatile midgame. But that’s not a fix to the actual problem. The current Hydralisks and Spores are fine as they are. Attention should be directed towards granting Zerg a way to defeat Spore/Viper/SH/Infestor with a more expensive army. Making the Brood Lord immune to abduct would solve the problem without messing with the other match-ups. I hope the developers will give this option a chance.I don’t like those changes that much, they don’t seem that necessary. I’m pretty okay with how ZvZ is at the moment so I can’t think of any good changes to be honest. The turtle style we’ve seen a bunch of time hasn’t happened to me yet, so maybe that’s why!It’s a very small change which would probably leave Swarm Hosts in ZvZ close to unaffected. Brood Lords would be more viable but in the late game I still think they would not work against mass spores and vipers + queens for transfuse. You need to push with your Brood Lords so you will get abducted every time anyway and you can’t really break the Swarm Host line in a reasonable amount of time with Brood Lords. I think mutas could work much better in ZvZ from this point so we would see Swarm Hosts less but I am not sure it would fix the problem since you can start from infestors or something else and then transition to Swarm Hosts. Mass muta play would be viable but it would be still risky and that’s not what you aim for in competitive play. You want to have a consistent way to beat a strategy.I think with the changes, mutas might become popular in ZvZ again, since roaches are superior right now and reign supreme. It could be worth testing out to see the effects, seems like an interesting idea.Rather than looking at Swarm Hosts, I think it would be better if they tweaked Infestors. Right now the range on fungal growth is 10, but I think it would be okay to decrease the range a little and give back its bonus damage vs. armor. Fungal becoming weak is the reason that all we’re seeing in ZvZ nowadays is all-roach fights.In the end, I don’t think Blizzard’s suggested fixes can change Swarm Host vs Swarm Host. If one player goes SH’s and the other player goes SH’s in response, having a long, stalemated game is inevitable. It’s just like in Brood War TvT, where if one player hunkers down with the intent of going for a long game, then you have no choice in following him along. I don’t think a change is needed.It seems like the fix is aimed at Stephano’s recent games. But if you look at Korean leagues where the highest level of competition is at, it’s hard to find those kind of SH games because Zerg players play a very tight game and are quick to notice tech switches. If Stephano played Korean players, I don’t think he’d be able to play that type of game. I don’t think ZvZ needs any kind of patch.If you make mutas easier to use, you’ll see more Swarm Host use. It seems like where would be less roach vs roach games , and more muta vs muta ,or muta vs Swarm Host games.There are barely any games where you see Swarm Host vs. Swarm Host. There’s nothing I want changed in particular.

See also  [Update] One of America’s biggest gaming companies is acting as China’s censor | blitzchung - Vietnamnhanvan

Do you think there is a problem with Swarm Hosts in ZvT?

[image loading] Liquid`Snute: They are strong but they have to be, to fight Mech. I don’t think I can answer this well.

[image loading] Liquid`TLO: I don’t think so, they’re necessary vs mech and not really great vs bio. They can be useful vs bio-mech but I don’t see any game breaking problem with them.

[image loading] Acer.Nerchio: ZvT is probably match up that is affected the least by Swarm Hosts since they are primarily used in situations to fight mech and even then it’s usually only a few Swarm Hosts not the amounts you see in other match ups. If you want to balance Swarm Hosts you should probably almost ignore ZvT since it has very little play and any changes will not matter that much here since Terran will always have superior army in the late game with mass air.

[image loading] coL.Hendralisk: SH are only viable vs mech, and without SH it seems mech is way too tough to handle. It causes for long games but without another change, SH is an effective way to deal with mech.

[image loading] Roccat_HyuN: I think they’re fine.

[image loading] CJ_Hydra: I don’t think there is a problem.

[image loading] SKT_soO: No problem.

[image loading] AX.Impact: Not in particular.

They are strong but they have to be, to fight Mech. I don’t think I can answer this well.I don’t think so, they’re necessary vs mech and not really great vs bio. They can be useful vs bio-mech but I don’t see any game breaking problem with them.ZvT is probably match up that is affected the least by Swarm Hosts since they are primarily used in situations to fight mech and even then it’s usually only a few Swarm Hosts not the amounts you see in other match ups. If you want to balance Swarm Hosts you should probably almost ignore ZvT since it has very little play and any changes will not matter that much here since Terran will always have superior army in the late game with mass air.SH are only viable vs mech, and without SH it seems mech is way too tough to handle. It causes for long games but without another change, SH is an effective way to deal with mech.I think they’re fine.I don’t think there is a problem.No problem.Not in particular.

Do you think there is a problem with Swarm Hosts in ZvP?

[image loading] Liquid`Snute: The locusts’ range/movement speed off creep might be a bit too strong. But again, the Swarm Host is a necessity.

[image loading] Liquid`TLO: There aren’t really any other viable late game compositions for Zerg that can fight cost efficient in any way, especially off creep. High level Protoss players are very good at dealing damage and mass expanding vs Swarm Host, so I don’t think there’s a problem here necessarily. If Swarm Host were weakened you’d need to address a lot of other units at the same time though.

[image loading] Acer.Nerchio: There is a problem with Swarm Hosts in ZvP but there is definitely a counter play to it, so the approach should be different than in ZvZ. Very much the same as ZvT, Protoss has stronger late game army than Zerg with mass air (usually Tempest) and Templars but there is no reason why Protoss player should attack a Swarm Host Zerg that is simply sitting in his base. That doesn’t work in his favour and he will gain more by sitting in his base himself which leads to terrible stalemates (Mana vs Firecake come up to mind, Mana tried attacking here and there so he lost eventually but he didn’t have to).

[image loading] coL.Hendralisk: Similarly, long drawn out games where seemingly both sides aren’t hard pressed to attack. Sort of like vs mech, I feel vs airtoss going SH is a solid response and it would be hard to deal with it otherwise. I don’t really go SH enough myself to comment more on SHs.

[image loading] Roccat_HyuN: I think they’re fine.

[image loading] CJ_Hydra: I don’t think there is a problem.

[image loading] SKT_soO: It’s so hard to use Swarm Hosts in ZvP.

[image loading] AX.Impact: Not really.

The locusts’ range/movement speed off creep might be a bit too strong. But again, the Swarm Host is a necessity.There aren’t really any other viable late game compositions for Zerg that can fight cost efficient in any way, especially off creep. High level Protoss players are very good at dealing damage and mass expanding vs Swarm Host, so I don’t think there’s a problem here necessarily. If Swarm Host were weakened you’d need to address a lot of other units at the same time though.There is a problem with Swarm Hosts in ZvP but there is definitely a counter play to it, so the approach should be different than in ZvZ. Very much the same as ZvT, Protoss has stronger late game army than Zerg with mass air (usually Tempest) and Templars but there is no reason why Protoss player should attack a Swarm Host Zerg that is simply sitting in his base. That doesn’t work in his favour and he will gain more by sitting in his base himself which leads to terrible stalemates (Mana vs Firecake come up to mind, Mana tried attacking here and there so he lost eventually but he didn’t have to).Similarly, long drawn out games where seemingly both sides aren’t hard pressed to attack. Sort of like vs mech, I feel vs airtoss going SH is a solid response and it would be hard to deal with it otherwise. I don’t really go SH enough myself to comment more on SHs.I think they’re fine.I don’t think there is a problem.It’s so hard to use Swarm Hosts in ZvP.Not really.

Do you think that Zerg currently have an advantage in ZvT?

[image loading] Liquid`Snute: Yes, on big maps. ZvT is very map dependant and the new maps are quite big and slightly Zerg favored.

[image loading] Liquid`TLO: The maps are currently very good for Zerg, we went from extremely small maps with many chokes like Yeonsu and Heavy rain to mostly very big open wide maps, so naturally balance shifted towards Zerg. I’d like to see a bit more of a mixed map pool with small medium and big maps.

[image loading] Acer.Nerchio: I don’t think there is a problem in ZvT and even if there is, the advantage for Z is really small. I don’t quite understand why Terrans don’t use the typical bio mine composition that often anymore because it was really good in the past. I believe people follow patterns a little bit too much so if there is a Korean player in a big tournament that shows something else like bio mech then he changes the meta game for the next few months.

[image loading] coL.Hendralisk: It feels that way on certain maps, when Zergs defend early harass without much problem and race up to a really high drone count and go into muta ling bane. With a critical mass of mutas, Terran have a hard time dealing with that. But Zerg needs a lot of mechanics to pull that off smoothly, so it’s not like camping with infestor Brood Lord or something along those lines.

[image loading] Roccat_HyuN: It feels like Zerg is a little bit better, but because Terrans keep trying a lot of new things it seems like things are evening out. For instance, starting mech and going into bio-mech, or opening bio and adding in mech units late. I think it would be alright to leave it as is for now and keep and eye on it.

[image loading] CJ_Hydra: I think Zerg have a slight advantage.

[image loading] SKT_soO: Zerg have a slight advantage.

[image loading] AX.Impact: Most Terrans think that it’s good for Zerg, but if you understand the game well there’s actually nothing that’s especially good for Zerg.

Yes, on big maps. ZvT is very map dependant and the new maps are quite big and slightly Zerg favored.The maps are currently very good for Zerg, we went from extremely small maps with many chokes like Yeonsu and Heavy rain to mostly very big open wide maps, so naturally balance shifted towards Zerg. I’d like to see a bit more of a mixed map pool with small medium and big maps.I don’t think there is a problem in ZvT and even if there is, the advantage for Z is really small. I don’t quite understand why Terrans don’t use the typical bio mine composition that often anymore because it was really good in the past. I believe people follow patterns a little bit too much so if there is a Korean player in a big tournament that shows something else like bio mech then he changes the meta game for the next few months.It feels that way on certain maps, when Zergs defend early harass without much problem and race up to a really high drone count and go into muta ling bane. With a critical mass of mutas, Terran have a hard time dealing with that. But Zerg needs a lot of mechanics to pull that off smoothly, so it’s not like camping with infestor Brood Lord or something along those lines.It feels like Zerg is a little bit better, but because Terrans keep trying a lot of new things it seems like things are evening out. For instance, starting mech and going into bio-mech, or opening bio and adding in mech units late. I think it would be alright to leave it as is for now and keep and eye on it.I think Zerg have a slight advantage.Zerg have a slight advantage.Most Terrans think that it’s good for Zerg, but if you understand the game well there’s actually nothing that’s especially good for Zerg.

What do you think of Blizzard’s proposed change to hellion/hellbats? Are there any other changes that you would like to see?

[image loading] Liquid`Snute: It’s okay don’t have too many comments on this one.

[image loading] Liquid`TLO: I think that could be fun, I’m a bit concerned there could be some too strong hellbat marine medivac timings, especially if Terran does only the slightest early game dmg and retains his hellions but so far the servos are completely useless so it’s a good thing to try out in my opinion.

[image loading] Acer.Nerchio: I think it won’t affect almost anything in the game. There might be a few timings in ZvT that might be a little bit stronger like standard hellion opening followed up with 2 medivacs with marines but instead of 6 hellions you will have 6 hellbats.

I would like mothership core to be less relevant in the game because now it is main offensive and defensive unit for Protoss in all match ups along with the sentry and allows for too quick change between defensive and offensive stance. Especially in PvZ you can pressure with very small army that should be defending your base and not attacking and yet you cannot be punished for that.

[image loading] coL.Hendralisk: It will help out Terrans some, though I am worried about the first push in tvz with medivacs will be a lot stronger. Not really too sure on what other changes atm, I usually like to see how things are after balance changes to judge from there.

See also  Top 7 Double Barrel Shotguns 2021 | double barrel shotgun

[image loading] Roccat_HyuN: I think it could become very tough for Zerg at the 2-medivac timing.

[image loading] CJ_Hydra: It would be an alright patch. The other races wouldn’t be able to go for greedy play so comfortably because of early-mid game rushes with hellions transformed into hellbats.

[image loading] SKT_soO: I don’t know exactly how it would turn out, but it would definitely help Terran in the match-up.

[image loading] AX.Impact: I think we’ll see a wide variety of strategies. If Terrans can use them well, there will be situations where Zerg will be at a disadvantage even if they stop an attack. Still, I’d have to play it out first to know for sure.

It’s okaydon’t have too many comments on this one.I think that could be fun, I’m a bit concerned there could be some too strong hellbat marine medivac timings, especially if Terran does only the slightest early game dmg and retains his hellions but so far the servos are completely useless so it’s a good thing to try out in my opinion.I think it won’t affect almost anything in the game. There might be a few timings in ZvT that might be a little bit stronger like standard hellion opening followed up with 2 medivacs with marines but instead of 6 hellions you will have 6 hellbats.I would like mothership core to be less relevant in the game because now it is main offensive and defensive unit for Protoss in all match ups along with the sentry and allows for too quick change between defensive and offensive stance. Especially in PvZ you can pressure with very small army that should be defending your base and not attacking and yet you cannot be punished for that.It will help out Terrans some, though I am worried about the first push in tvz with medivacs will be a lot stronger. Not really too sure on what other changes atm, I usually like to see how things are after balance changes to judge from there.I think it could become very tough for Zerg at the 2-medivac timing.It would be an alright patch. The other races wouldn’t be able to go for greedy play so comfortably because of early-mid game rushes with hellions transformed into hellbats.I don’t know exactly how it would turn out, but it would definitely help Terran in the match-up.I think we’ll see a wide variety of strategies. If Terrans can use them well, there will be situations where Zerg will be at a disadvantage even if they stop an attack. Still, I’d have to play it out first to know for sure.

Thanks to Stephano and a few highly visible Swarm Host stalemates, Blizzard is considering acting upon Heart of the Swarm’s most controversial unit. At the same time, ZvT at the competitive level appears to be trending in Zerg’s favor, which has caught Blizzard’s attention as well. After putting forth some ideas, Blizzard finally released a balance test map on May 14th with the following changes:TeamLiquid asked Zerg pros from across all three WCS regions their thoughts on Blizzard’s proposed changes.We talked to the playersthe release of the test map, butBlizzard had released their proposed changes.Maybe there’s a Terran questionnaire coming soon.


[NEW] Helix Core server configuration for Swarm | swarm host – Vietnamnhanvan

Helix Core server

configuration for

Swarm

Now that you have a configured instance of Swarm, the last piece is to configure your Helix server to tell Swarm about interesting events. This is accomplished through the use of triggers.

For more information about Helix server triggers, see Using triggers to customize behavior in .

Important

Swarm does not support Helix servers configured to use P4AUTH, see Centralized authentication server (P4AUTH) in the .

Note

  • Helix Core server

    can refer to a

    Helix server

    machine (

    P4D

    ), proxy, broker, replica, edge server, or commit server.
    For simplicity, the term

    Helix server

    is used to refer to any configuration of a

    Helix Core server

    machine.

  • Swarm

    can be connected to

    Helix server

    s (

    P4D

    ) and commit servers.

  • To configure Swarm to connect to more than one Helix server (P4D), see Multiple-Helix server instances.

    To configure Swarm to connect to a Helix server configured to use , see Commit-edge deployment.

  • Swarm

    must not be connected to

    Helix

    Broker,

    Helix

    Proxy,

    Helix

    Edge, forwarding replica, or read-only replica servers.

Using triggers to push events to

Swarm

Helix server provides a facility called to customize the operation of the server, or to invoke additional processing for specific kinds of versioning operations. Swarm provides a trigger script written in Perl that notifies Swarm about activity within the Helix server.

See Trigger options for more information on configuring the Perl trigger.

Set up

Swarm

triggers with a Windows or Linux-hosted

Helix server

Tip

Many of the steps in this procedure are common to both Windows and Linux-hosted Helix servers. When there is a difference between the Windows and Linux operating systems, this is indicated in the procedure.

  1. Ensure that the required Trigger dependencies have been installed on the machine hosting the

    Helix server

    .

  2. Copy the

    Swarm

    trigger to the

    Helix server

  • If your

    Helix server

    is version 2014.1 (or later), we recommend submitting the trigger script, p4-bin/scripts/swarm-trigger.pl, to

    Helix server

    and running it from the depot. The recommended depot location is //.swarm/triggers/swarm-trigger.pl, especially if you have already setup Comment attachments.

  • If your

    Helix server

    is older than version 2014.1, or you prefer that the trigger file exist in the filesystem, you must copy the p4-bin/scripts/swarm-trigger.pl script to the server hosting

    Helix server

    . If your

    Helix server

    deployment uses the commit-edge architecture, the script must also be copied to all edge servers, and it must exist in the same path on all servers.

Note

If you are using the Swarm OVA, the full path to the trigger script within the OVA’s filesystem is: /opt/perforce/swarm/p4-bin/scripts/swarm-trigger.pl.

  • Configure the trigger.

  • You need to use the API token established in the Establish trigger token.

    swarm-trigger.pl can be configured directly, but the preferred approach is to create a configuration file called swarm-trigger.conf. Using the configuration file greatly simplifies upgrades.

    • If you are using the

      Swarm

      triggers package described in Install and configure Swarm from a package, the configuration file is available at /opt/perforce/etc/swarm-trigger.conf

      • If you submitted the trigger script to the depot in the previous step, you should similarly submit the configuration file to the depot. The recommended depot location is //.swarm/triggers/swarm-trigger.conf.
      • If you copied the trigger script to the commit server and all edge servers in the previous step, also copy the configuration file to the commit server and all edge servers, making sure that they exist in the same path on all servers.
    • If you are not using the

      Swarm

      trigger package, create swarm-trigger.conf in the same directory as swarm-trigger.pl.

      • If you submitted the trigger script to the depot in the previous step, you should similarly submit the configuration file to the depot. The recommended depot location is //.swarm/triggers/swarm-trigger.conf.
      • If you copied the trigger script to the commit server and all edge servers in the previous step, also copy the configuration file to the commit server and all edge servers, making sure that they exist in the same path on all servers.

    The following is a sample of what your swarm-trigger.conf should contain:

    # SWARM_HOST (required)
    # Hostname of your Swarm instance, with leading "http://" or "https://".
    SWARM_HOST=""
    
    # SWARM_TOKEN (required)
    # The token used when talking to Swarm to offer some security. To obtain the
    # value, log in to Swarm as a super user and select 'About Swarm' to see the
    # token value.
    SWARM_TOKEN=""
    
    # ADMIN_USER (optional) Do not use if the Workflow feature is enabled (default)
    # For enforcing reviewed changes, optionally specify the normal Perforce user
    # with admin privileges (to read keys); if not set, will use whatever Perforce
    # user is set in environment.
    ADMIN_USER=
    
    # ADMIN_TICKET_FILE (optional) Do not use if the Workflow feature is enabled (default)
    # For enforcing reviewed changes, optionally specify the location of the
    # p4tickets file if different from the default ($HOME/.p4tickets).
    # Ensure this user is a member of a group with an 'unlimited' or very long
    # timeout; then, manually login as this user from the Perforce server machine to
    # set the ticket.
    ADMIN_TICKET_FILE=				
    				
    # VERIFY_SSL (optional)
    # If HTTPS is being used on the Swarm web server, then this controls whether
    # the SSL certificate is validated or not. By default this is set to 1, which
    # means any SSL certificates must be valid. If the web server is using a self
    # signed certificate, then this must be set to 0.
    VERIFY_SSL=1

    Modify the swarm-trigger.conf configuration file to set the SWARM_HOST and the SWARM_TOKEN variables appropriately.

    Note

    Windows only:

    You may need to edit the trigger script to specify the full path to curl.exe if the HTTP::Tiny module is not installed.

    Note

    Linux only:

    swarm-trigger.pl looks for configuration in the following files. Variables defined in the later files will override the earlier defined variables of the same name:

    • Variables set inside the swarm-trigger.pl script itself
    • /etc/perforce/swarm-trigger.conf

    • /opt/perforce/etc/swarm-trigger.conf

    • The swarm-trigger.conf file stored in the same directory as swarm-trigger.pl.
    • Any file passed to the swarm-trigger.pl script using the -c command line argument

    Important

    Windows and Linux:

    If you specify ADMIN_USER, the ticket contained in %USERPROFILE%/p4tickets.txt (Windows), $HOME/.p4tickets (Linux), or the optional ticket file specified with the ADMIN_TICKET_FILE must use the port that was used to start Helix server. For example, if p4d is started with:

    C:\>

    p4d -p my-helix-core-server:1666 ...

    then the ticket for the admin user specified with ADMIN_USER should be established with:

    C:\>

    p4 -p my-helix-core-server:1666 -u admin_userid login

    If the ticket was established using the wrong port, the error message you encounter includes the port that the trigger is attempting to use:

    'swarm.strict.1' validation failed: Invalid login credentials to [port] within this trigger script; please contact your administrator.
  • Linux only: Ensure that the script has execute permissions.

    Important

    Skip this step if you have committed the script to the Helix server.

    $

    chmod +x /path/to/swarm-trigger.pl
  • Verify that the trigger script executes correctly.

    • For Windows:
    • Run:

    C:\>

    perl "C:\path\to\swarm-trigger.pl" -t ping -v 0

    Use the full path to perl if it is not available in your command path.

    You should expect to see no output. If the trigger is misconfigured, such as using an invalid trigger token, you would see an error.

    Warning

    Only if using Curl:

    Installation of the triggers may cause a security warning dialog to appear when curl.exe executes:

    If this occurs, the triggers hang, creating zombie Perl processes. Due to the way triggers are invoked by Helix server, the dialog is normally not visible even though Windows is waiting on interaction.

    To resolve this:

    1. Clear the Always ask before opening this file check box and click Run.
    2. Right-click curl.exe, select Properties, and click Unblock.
    • For Linux:
    • Important

      Skip this step if you have committed the script to the Helix server.

      $

      /path/to/swarm-trigger.pl -t ping -v 0

      You should expect to see no output. If the trigger is misconfigured, such as using an invalid trigger token, you would see an error.

      Note

      Run the trigger script without any arguments to see additional usage information.

    • Update the Helix server triggers table to run the trigger script.

      Warning

      • The swarm.shelvedel shelve-delete trigger line was added to Swarm in version 2018.1 and updated in version 2020.1.

        • New installation or upgrading from

          Swarm

          2017.4 and earlier: add the swarm.shelvedel shelve-delete trigger line to the

          Helix server

          trigger table if it is not already present.

        • Upgrading from

          Swarm

          2018.x and 2019.x: replace the existing swarm.shelvedel shelve-delete trigger line in the

          Helix server

          trigger table with the one supplied in the

          Swarm

          version you are upgrading to.

      • Workflow feature:
      • The Workflow feature is enabled by default in Swarm 2019.2 and later. The trigger lines required when workflow is enabled are different to those required when workflow is disabled:

        • Workflow feature enabled (default):
          • Comment out the

            swarm.enforce.1

            ,

            swarm.enforce.2

            ,

            swarm.strict.1

            , and

            swarm.strict.2

            trigger lines in the

            Helix server

            trigger table if they are present.

          • Add the swarm.enforce change-submit, swarm.strict change-content, and swarm.shelvesub shelve-submit trigger lines to the

            Helix server

            trigger table if they are not already present.

        • Workflow feature disabled:
          • Comment out the swarm.enforce change-submit, swarm.strict change-content, and swarm.shelvesub shelve-submit trigger lines in the

            Helix server

            trigger table if they are present.

          • The

            swarm.enforce.1

            ,

            swarm.enforce.2

            ,

            swarm.strict.1

            , and

            swarm.strict.2

            trigger lines are commented out because they are optional. They require that the

            DEPOT_PATH1

            and

            DEPOT_PATH2

            values are configured appropriately. Support for these triggers will be dropped in a later release.

            • The first two lines configure the

              enforce

              feature, which rejects any submitted changes that are not tied to an approved review.

            • The second two lines configure the

              strict

              feature, which rejects any submitted changes when the contents of the changelist do not match the contents of its associated approved review.

          • If you need to apply

            enforce

            or

            strict

            to more depot paths, copy the lines and tweak the depot paths as necessary.

      Tip

      The trigger script can provide the list of trigger lines that should work, with little to no adjustment, by executing it with the -o option:

      Windows

      C:\>

      perl "C:\path\to\swarm-trigger.pl" -o

      Linux

      $

      /path/to/swarm-trigger.pl -o

      Tip

      • The %quote%c:\path\to\perl.exe%quote% entry is only required for Windows-hosted systems.
      • An initial tabbed indent is required for each trigger line.
      • Commented out trigger lines are not stored.
      • If you disable the workflow feature in the Swarm config.php file, workflow will not be processed by Swarm but a small overhead is still incurred by the Helix server each time it runs a workflow trigger script. This overhead can be eliminated by commenting out the swarm.enforce change-submit, swarm.strict change-content, and swarm.shelvesub shelve-submit workflow triggers.

      As a Helix server user with privileges, edit the Helix server trigger table by running the p4 triggers command and add the following lines (including the initial tab character). Update the perl.exe, trigger script, and configuration file paths in each line below to reflect the actual paths on your Helix server:

      1. If you have committed both the trigger script and the configuration file to the

        Helix server

        :

        	swarm.job        form-commit   job    "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t job        -v %formname%"
        	swarm.user       form-commit   user   "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t user       -v %formname%"
        	swarm.userdel    form-delete   user   "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t userdel    -v %formname%"
        	swarm.group      form-commit   group  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t group      -v %formname%"
        	swarm.groupdel   form-delete   group  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t groupdel   -v %formname%"
        	swarm.changesave form-save     change "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t changesave -v %formname%"
        	swarm.shelve     shelve-commit  //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t shelve     -v %change%"
        	swarm.commit     change-commit  //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t commit     -v %change%"
        	swarm.shelvedel  shelve-delete  //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t shelvedel  -v %change% -w %client% -u %user% -d %quote%%clientcwd%^^^%quote% -a %quote%%argsQuoted%%quote% -s %quote%%serverVersion%%quote%"
        #	The following three triggers are used by workflow. If workflow is disabled in the Swarm
        #	configuration then they should be disabled.
        	swarm.enforce    change-submit  //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t checkenforced -v %change% -u %user%"
        	swarm.strict     change-content //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t checkstrict   -v %change% -u %user%"
        	swarm.shelvesub  shelve-submit  //...  "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t checkshelve   -v %change% -u %user%"
        #	The following triggers are only used to prevent a commit without an approved review.
        #	They predate the workflow functionality and should only be used if workflow is disabled.
        #	Support for these will be dropped in a later release.
        #	swarm.enforce.1 change-submit  //DEPOT_PATH1/... "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t enforce -v %change% -p %serverport%"
        #	swarm.enforce.2 change-submit  //DEPOT_PATH2/... "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t enforce -v %change% -p %serverport%"
        #	swarm.strict.1  change-content //DEPOT_PATH1/... "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t strict -v %change% -p %serverport%"
        #	swarm.strict.2  change-content //DEPOT_PATH2/... "%quote%c:\path\to\perl.exe%quote% %//.swarm/triggers/swarm-trigger.pl% -c %//.swarm/triggers/swarm-trigger.conf% -t strict -v %change% -p %serverport%"
        
      2. If you have copied the trigger script and configuration file to common paths on all servers:
      3. 	swarm.job        form-commit   job    "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t job        -v %formname%"
        	swarm.user       form-commit   user   "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t user       -v %formname%"
        	swarm.userdel    form-delete   user   "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t userdel    -v %formname%"
        	swarm.group      form-commit   group  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t group      -v %formname%"
        	swarm.groupdel   form-delete   group  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t groupdel   -v %formname%"
        	swarm.changesave form-save     change "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t changesave -v %formname%"
        	swarm.shelve     shelve-commit  //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t shelve     -v %change%"
        	swarm.commit     change-commit  //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t commit     -v %change%"
        	swarm.shelvedel  shelve-delete  //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t shelvedel  -v %change% -w %client% -u %user% -d %quote%%clientcwd%^^^%quote% -a %quote%%argsQuoted%%quote% -s %quote%%serverVersion%%quote%"
        #	The following three triggers are used by workflow. If workflow is disabled in the Swarm
        #	configuration then they should be disabled.
        	swarm.enforce    change-submit  //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t checkenforced -v %change% -u %user%"
        	swarm.strict     change-content //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t checkstrict   -v %change% -u %user%"
        	swarm.shelvesub  shelve-submit  //...  "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t checkshelve   -v %change% -u %user%"							
        #	The following triggers are only used to prevent a commit without an approved review.
        #	They predate the workflow functionality and should only be used if workflow is disabled.
        #	Support for these will be dropped in a later release.
        #	swarm.enforce.1 change-submit  //DEPOT_PATH1/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t enforce -v %change% -p %serverport%"
        #	swarm.enforce.2 change-submit  //DEPOT_PATH2/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t enforce -v %change% -p %serverport%"
        #	swarm.strict.1  change-content //DEPOT_PATH1/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t strict -v %change% -p %serverport%"
        #	swarm.strict.2  change-content //DEPOT_PATH2/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t strict -v %change% -p %serverport%"
        

      Warning

      Windows and Linux:

      The use of %quote% is not supported on 2010.2 servers (it is harmless though); if you are using this version, ensure that you do not have any spaces in the path to perl.exe or the script’s path.

      Important

      Workflow feature disabled:

      If your Helix server has SSL enabled and is older than the 2014.1 release, the %serverport% trigger variable does not include the necessary transport indicator, which can cause the enforce and strict triggers to fail.

      To solve this problem, add ssl: immediately before %serverport% in the trigger lines. For example:

      #	The following triggers are only used to prevent a commit without an approved review.
      #	They predate the workflow functionality and should only be used if workflow is disabled.
      #	Support for these will be dropped in a later release.
      #	swarm.enforce.1 change-submit  //DEPOT_PATH1/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t enforce -v %change% -p ssl:%serverport%"
      #	swarm.enforce.2 change-submit  //DEPOT_PATH2/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t enforce -v %change% -p ssl:%serverport%"
      #	swarm.strict.1  change-content //DEPOT_PATH1/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t strict -v %change% -p ssl:%serverport%"
      #	swarm.strict.2  change-content //DEPOT_PATH2/... "%quote%C:\path\to\perl.exe%quote% %quote%/path/to/swarm-trigger.pl%quote% -c %quote%/path/to/swarm-trigger.conf%quote% -t strict -v %change% -p ssl:%serverport%"
    • Configure the Helix server to promote all shelved changes.

      When this configurable is set, Swarm has access to all shelved changelists, which is a requirement for pre-commit reviews. When it is not set, users connected to an edge server must remember to use the -p option when shelving files to promote their shelves to the commit server when initiating a pre-commit review.

      p4 configure set dm.shelve.promote=1
    • Optionally forward logins to the commit server.

      If you intend to use P4V and its Swarm integration, you should consider forwarding logins to the commit server. See P4V Authentication for details.

    • You can now configure additional functionality for

      Swarm

      :

      • Optional: Hide

        Swarm

        storage from regular users, see Hiding Swarm storage from regular users.

      • Optional: Handle exclusive locks, see Handling Exclusive Locks.
    • Depending on your installation type, do one of the following:
      • Swarm

        package installation: Review the post-install configuration options to customize your

        Swarm

        installation, see Post-install configuration options.

      • Swarm

        OVA installation: Review the post-install configuration options to customize your

        Swarm

        installation, see Post-install configuration options.

      • Swarm

        tarball installation: Set up a recurring task to spawn workers, see Set up a recurring task to spawn workers.

      Hiding

      Swarm

      storage from regular users

      Swarm information storage uses Helix server’s keys facility. By default, users with -level access can search keys and potentially obtain information they would not otherwise have access to, and users with -level access can write or modify keys potentially corrupting or destroying data.

      We recommend that you set the dm.keys.hide configurable to 2 to require -level access for searching and modifying keys. Note that dm.keys.hide is available in Helix server versions 2013.1 and newer.

      When dm.keys.hide is set to 2, both the p4 keys and p4 key commands require -level access in the Helix server. When dm.keys.hide is set to 1, only the p4 keys command requires -level access in the Helix server. When dm.keys.hide is set to 1, or is not set, users who know (or can deduce) key names can read values (if they have -level access) or write values (if they have -level access) with the p4 key command.

      To set dm.keys.hide:

      $

      p4 configure set dm.keys.hide=2

      To confirm the current value of dm.keys.hide:

      $

      p4 configure show dm.keys.hide

      To unset dm.keys.hide:

      $

      p4 configure unset dm.keys.hide

      Handling Exclusive Locks

      Swarm takes copies of files when it is creating reviews. Some of the files managed by Helix server may be limited to ‘exclusive open’ by having the filetype modifier ‘+l’ set. This file-level setting ensures only one user at a time can open the file for editing.

      To allow Swarm to work with these ‘exclusive open’ files, you must enable filetype.bypasslock in the Helix server configuration.

      To set filetype.bypasslock:

      $

      p4 configure set filetype.bypasslock=1

      To confirm the current value of filetype.bypasslock:

      $

      p4 configure show filetype.bypasslock

      To unset filetype.bypasslock:

      $

      p4 configure unset filetype.bypasslock

      If this setting is not enabled in Helix server, Swarm will report exceptions when working with exclusively opened files similar to “Cannot unshelve review (x). One or more files are exclusively open”, and noting that you must have the filetype.bypasslock configurable enabled.


      ONE Base Swarm Host \u0026 Infestors? | ONLY Proxy to Grandmaster #5


      Feel free to let me know if you have any suggestions for future videos. Enjoy this one and have a great day 🙂
      If you are enjoying my YouTube content, check out my live stream on Twitch!
      Streaming pretty much every day, starting time is at 3 PM CET. Link to my stream is down below.
      ►Twitch: https://www.twitch.tv/beastyqt
      ►Twitter: https://twitter.com/BeastyqtSC2
      ►Merchandise: https://chrysosmerch.com/collections/beastyqt
      ►Instagram: https://www.instagram.com/beastyqtsc2
      ►Patreon: https://www.patreon.com/beastyqt
      ►Discord: https://discord.gg/aJMGAEn
      Beastyqt StarCraft2 SC2
      Intro and End Screen designed by VincenteIL: https://www.youtube.com/VincenteIL
      Thanks for watching and supporting! 🙂

      นอกจากการดูบทความนี้แล้ว คุณยังสามารถดูข้อมูลที่เป็นประโยชน์อื่นๆ อีกมากมายที่เราให้ไว้ที่นี่: ดูเพิ่มเติม

      ONE Base Swarm Host \u0026 Infestors? | ONLY Proxy to Grandmaster #5

      Swarm Technology, Ants, Robots, IoT and Parallel Processing


      Swarm Technology’s strategically important issued patents define the architecture for PlugandPlay IntentBased Autonomy, Proactive Autonomy, and Heterogeneous Interoperability in networking and robotics.
      The video describes swarm behavior in ants and transposes the algorithm into robotics. The same technology is applicable to IntentBased Networks, and Heterogeneous IoT Edge Processing.
      See more here: http://www.swarmtechnology.us/
      Patent information is located here: http://www.swarmtechnology.us/patents

      Swarm Technology, Ants, Robots, IoT and Parallel Processing

      Rogue’s Swarm Hosts! – SC2 Proleague


      Subscribe to SC2HL ➜ http://bit.ly/subscribeSC2HL
      ► http://bit.ly/DivisionZero Get the BEST quality gaming gear at Division Zero Gaming!
      ► http://bit.ly/Chairs4gaming Get $20 discount and at Chairs4Gaming using code \”SC2HL\”

      Jin Air Rogue is going for Swarmhost in his match vs Dark during the Starcraft 2 proleague! A unit that we rarely see anymore!
      Thank you for watching our highlights and other videos! Subscribe for a lot more cool content!

      StarCraft 2: Legacy of the Void is a standalone expansion pack to the military science fiction realtime strategy game StarCraft 2: Wings of Liberty, and the third part of the StarCraft 2 trilogy developed by Blizzard Entertainment. On this channel you will find Starcraft funny moments, micro, highlights, plays and a lot more!

      Rogue's Swarm Hosts! - SC2 Proleague

      Serral’s MASS SWARM HOSTS vs. Neeb – Starcraft 2


      Serral going for Lots of free units and lots of Swarm hosts in a Protoss vs. Zerg series vs. Neeb.
      Watch the Starcraft 2 ESL Pro Tour 2020: http://twitch.tv/esl_sc2
      ► SUBSCRIBE to SC2HL! http://bit.ly/SC2HLsubscribe \r
      \r
      Thank you for watching our videos! Subscribe for more StarCraft 2: Legacy of the void highlights. We also upload other content, such as trailers \u0026 montages.\r
      \r
      StarCraft 2: Legacy of the Void is a standalone expansion pack to the military science fiction realtime strategy game StarCraft 2: Wings of Liberty, and the third part of the StarCraft 2 trilogy developed by Blizzard Entertainment. On this channel you will find Starcraft funny moments, micro, highlights, plays and a lot more! starcraft 2 vods

      Serral's MASS SWARM HOSTS vs. Neeb - Starcraft 2

      Mass Carriers \u0026 Mass oracles in a PRO match?! – Starcraft 2


      Has goes for his typical strategies, building mass carriers \u0026 mass oracles versus elazer in a crazy Protoss vs Zerg. Has is one of the few players going for mass oracles and mass carriers in a pro match
      ► http://bit.ly/SC2HLsubscribe Subscribe to SC2HL
      ► http://bit.ly/SC2HLdonate Like our channel? Consider supporting us by donating
      Thank you for watching our videos! Subscribe for more StarCraft 2: Legacy of the void highlights. We also upload other content, such as trailers \u0026 montages.
      StarCraft 2: Legacy of the Void is a standalone expansion pack to the military science fiction realtime strategy game StarCraft 2: Wings of Liberty, and the third part of the StarCraft 2 trilogy developed by Blizzard Entertainment. On this channel you will find Starcraft funny moments, micro, highlights, plays and a lot more!

      Mass Carriers \u0026 Mass oracles in a PRO match?! - Starcraft 2

      นอกจากการดูบทความนี้แล้ว คุณยังสามารถดูข้อมูลที่เป็นประโยชน์อื่นๆ อีกมากมายที่เราให้ไว้ที่นี่: ดูวิธีอื่นๆWiki

      ขอบคุณมากสำหรับการดูหัวข้อโพสต์ swarm host

      Leave a Comment