I was really happy to see SC2 having a big, big patch that optimized (somehow?) SC2 - but it broke my map. As with every other big SC2 patch. However, unlike the errors of "Yesterday," this time the error seems so.... Vague. I can't seem to find what error is causing me to not be able to publish my map. Can anyone see an error here? Because for such a simple trigger, I'm not seeing it.
I was really happy to see SC2 having a big, big patch that optimized (somehow?) SC2 - but it broke my map. As with every other big SC2 patch. However, unlike the errors of "Yesterday," this time the error seems so.... Vague. I can't seem to find what error is causing me to not be able to publish my map. Can anyone see an error here? Because for such a simple trigger, I'm not seeing it.
*Check the photo*
Thanks in advance!
Thank you SC2Mapster's Discord for quickly answering my question! But now one more error remains - and this seems a bit more difficult. Can anyone see what's wrong with the trigger here? *Check the Photo*
I was really happy to see SC2 having a big, big patch that optimized (somehow?) SC2 - but it broke my map. As with every other big SC2 patch. However, unlike the errors of "Yesterday," this time the error seems so.... Vague. I can't seem to find what error is causing me to not be able to publish my map. Can anyone see an error here? Because for such a simple trigger, I'm not seeing it.
*Check the photo*
Thanks in advance!
Thank you SC2Mapster's Discord for quickly answering my question! But now one more error remains - and this seems a bit more difficult. Can anyone see what's wrong with the trigger here? *Check the Photo*
But once again, thanks to Talv in SC2Mapster's Discord this was fixed! Now there's another problem. What could be wrong here?
I was really happy to see SC2 having a big, big patch that optimized (somehow?) SC2 - but it broke my map. As with every other big SC2 patch. However, unlike the errors of "Yesterday," this time the error seems so.... Vague. I can't seem to find what error is causing me to not be able to publish my map. Can anyone see an error here? Because for such a simple trigger, I'm not seeing it.
*Check the photo*
Thanks in advance!
Thank you SC2Mapster's Discord for quickly answering my question! But now one more error remains - and this seems a bit more difficult. Can anyone see what's wrong with the trigger here? *Check the Photo*
But once again, thanks to Talv in SC2Mapster's Discord this was fixed! Now there's another problem. What could be wrong here?
Thank you Talv so much for your continuous answers! But once again, another problem struck me. This time, there was a "Pick Each Player" Trigger right above it, but this one still says something is wrong. So I added more and more "Pick Each Player" Triggers - and resulted in even more errors. What could be wrong here?
Thank you everyone who helped me to maintain my sanity throughout this *adventure.* I was able to fix this by correcting every "PICK EACH" triggers in the Editor.
Well... The cause was "Skip Remaining Actions" Trigger was considered the same thing as "x2 Returns." So removing "Skip Remaining Actions" triggers solved the issue.
Also, there were errors in the "Pick Each" triggers that the previous Editor ignored - but they are now being addressed properly. So all I had to do was fix them up by giving those triggers proper values and such.
Yea, describe please your solutions for the 4.0 related trigger fuckups.
As I said above, there were unseen errors with the "Pick Each Unit" and "Pick Each Player" Triggers. For example, the editor allowed the trigger to be like this:
Pick each unit in [HEROES] Group - Do Something for Picked Integer - Do Something for Picked Player - Do Something for Picked SOMETHING OTHER THAN UNITS
But now, the editor sees what's going on with this and makes you fix this by:
Pick each unit in [HEROES] Group - Do Something for Picked Unit - Do Something for Picked Unit - Do Something for Picked Unit
BUT. The only errors that were fixed was this "Picked" triggers. For others, its.... not working for me as well. That's why I announced to others out there that I'm DONE with map making. The errors are continuing... Without reason.
Solution was to not use *Picked X* outside of the loop definitions. But often times people had triggers bound so much to the old design that simply adapting to changed mechanics is not convenient.
Thus I put together library that can be used to revert what Blizzard did in relation to PickEach loops:
Hello again, SC2Mapster's Triggers Section!
I was really happy to see SC2 having a big, big patch that optimized (somehow?) SC2 - but it broke my map. As with every other big SC2 patch. However, unlike the errors of "Yesterday," this time the error seems so.... Vague. I can't seem to find what error is causing me to not be able to publish my map. Can anyone see an error here? Because for such a simple trigger, I'm not seeing it.
*Check the photo*
Thanks in advance!
Thank you everyone who helped me to maintain my sanity throughout this *adventure.* I was able to fix this by correcting every "PICK EACH" triggers in the Editor.
So what was the cause/solution?
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
In reply to DrSuperEvil:
Well... The cause was "Skip Remaining Actions" Trigger was considered the same thing as "x2 Returns." So removing "Skip Remaining Actions" triggers solved the issue.
Yea, describe please your solutions for the 4.0 related trigger fuckups.
In reply to Zolden:
Pick each unit in [HEROES] Group
- Do Something for Picked Integer
- Do Something for Picked Player
- Do Something for Picked SOMETHING OTHER THAN UNITS
- Do Something for Picked Unit
- Do Something for Picked Unit
- Do Something for Picked Unit
In reply to Zolden:
Solution was to not use *Picked X* outside of the loop definitions. But often times people had triggers bound so much to the old design that simply adapting to changed mechanics is not convenient.
Thus I put together library that can be used to revert what Blizzard did in relation to PickEach loops:
https://us.battle.net/forums/en/sc2/topic/20759576052
Previously known as: SomeoneTookMyNameTT