None.
Map Revealer Question
I was just wondering, is it possible to remove map revealers at specific locations? I've tried, but it won't seem to work.
We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch
nope. You can only remove all map revealers of a player.
You'll need to work with actual units if you want to remove them specifically.
For example constantly create an observer for that player and instantly remove it. It won't show in game, but it will generate vision.
You'll need to work with actual units if you want to remove them specifically.
For example constantly create an observer for that player and instantly remove it. It won't show in game, but it will generate vision.
How can I make it so that vision is only given to 1 or 2 specific units for each player, but nothing else owned by the player, I've tried things, but I always get either a blinking light issue or a slowed unit issue. Could I possibly mod map revealers?
None.
We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch
That's not possible, but there's a workaround:
Turn vision OFF to the player himself and give him vision to another (computer) player. This player must only own units in the spots you want the respective players to have vision to.
Turn vision OFF to the player himself and give him vision to another (computer) player. This player must only own units in the spots you want the respective players to have vision to.
I tried pretty much that, and I don't want to make a separate computer player for each player. I can kind of get it to work, but the lights randomly flash if two players are moving if I use map revealed, and when I use units if two players are too close they will slow down the units.
None.
I WAS ABLE TO FIX IT! Thanks for the help anyway.
None.
We can't explain the universe, just describe it; and we don't know whether our theories are true, we just know they're not wrong. >Harald Lesch
Remember that you can also use P9-12. They would be ideal for that purpose.
If you create/remove the unit every 3rd trigger loop the slowdown should be minimal. However there's still a small window for vision flash.
I remember a discussion with rockz about vision updating. If memory serves we concluded that the vision updates in fixed intervals after map start, so if you find that interval you can time your create/remove to the vision update so you only have to do it every 4s or so.
Also imaginable would be a clever grid system that keeps the vision giving unit away from the main unit(s). Combine it with a movement detection (center a 1x1 pixel location on the unit and check when it leaves) so you don't have to grid all the time which would also cause a slowdown.
EDIT:
OK, you got it, that's cool. But could you please tell us what was the problem / how you fixed it (for other people with similar problems)? Thanks
If you create/remove the unit every 3rd trigger loop the slowdown should be minimal. However there's still a small window for vision flash.
I remember a discussion with rockz about vision updating. If memory serves we concluded that the vision updates in fixed intervals after map start, so if you find that interval you can time your create/remove to the vision update so you only have to do it every 4s or so.
Also imaginable would be a clever grid system that keeps the vision giving unit away from the main unit(s). Combine it with a movement detection (center a 1x1 pixel location on the unit and check when it leaves) so you don't have to grid all the time which would also cause a slowdown.
EDIT:
OK, you got it, that's cool. But could you please tell us what was the problem / how you fixed it (for other people with similar problems)? Thanks
I do not usually deal with Vision when "Moving" map revealers.
I just remove all, and then create new ones at selected points on the map.
I just remove all, and then create new ones at selected points on the map.
None.
Options
Pages: 1
Back to forum
Please log in to reply to this topic or to report it.
Members in this topic: None.
[2026-6-23. : 3:29 am]
DarkenedFantasies -- Probably just didn't care. For example, at some point before release, they've updated the graphics of some of the Protoss buildings (Forge, CyberCore, Citadel, Observatory, Arbiter Tribunal), but instead of properly re-rendering them with edited 3D models, they did crappy copy-paste jobs on the rendered graphics.
[2026-6-21. : 4:56 am]
Ultraviolet -- I suppose we'll likely never know, but my guess would be that they already saw it operating successfully and there was no monetary incentive to finish the original work. And the dev cycle in old school Blizzard was so hectic, it's possible it just got forgotten about after the original game got released. Plus there's an element of existing MPQ files that were packaged with the original discs becoming outdated if they updated it. And it's not like they remade the original MPQs, they just made new ones for BW specifically[2026-6-21. : 4:26 am]
Oh_Man -- so that makes me think maybe the theory they are unfinished is not true and its a deliberate design decision, coz why not finish them wen ur making brood war?[2026-6-21. : 4:25 am]
Oh_Man -- the thing is thos buildings are from classic. that means they went ahead and made brood war without ever finishing the 'unfinished' buildings[2026-6-20. : 6:15 pm]
Ultraviolet -- Yeah he's talked about a lot of that stuff in his casts before. It seems plausible. Especially knowing how Blizzard of yesteryear operated.[2026-6-20. : 3:47 pm]
NudeRaider -- to clarify: couldn't recall the behavior for every single Protoss building but I was aware the disparity exists.[2026-6-20. : 3:43 pm]
NudeRaider -- Contained nothing new for me. Didn't know all building's behavior, but very much all unit's. Also Terran balance whine - also nothing new 
Members Online: NudeRaider, 
O)FaRTy1billion[MM]
NudeRaider, O)FaRTy1billion[MM]