- Joined
- Jun 7, 2016
- Messages
- 21
my custom entangled gold is working and all but, why does it keep showing "this mine is already entangled"
is that anyway to get rid of it??
is that anyway to get rid of it??
-
🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
-
🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece! 🔗 Click here to enter!
problem with entangled gold mine
- Status
- Joined
- Feb 5, 2009
- Messages
- 4,563
When does it show that?
I know that it can show "You cannot mine from Entangled Gold Mine" despite the custom unit then going to do just that, but I don't think I have seen the message you are describing just yet.
I know that it can show "You cannot mine from Entangled Gold Mine" despite the custom unit then going to do just that, but I don't think I have seen the message you are describing just yet.
- Joined
- Jun 7, 2016
- Messages
- 21
when i load my wisps in, it show "that gold is already entangled"
- Joined
- Feb 5, 2009
- Messages
- 4,563
That seems pretty weird, I appear to be having a similar issue in the same sort of situation, but a different message upon going to load the Wisps in. Your wisps don't have the Entangle Gold Mine ability at all, do they?
It might be possible that given our problems are similar but different, with the comparison of notes we could eliminate both problems.
UPDATE: I found that creating the worker unit based on the Wisp itself appears to trigger the same message that you have been encountering. As of yet, I don't know why it is doing that, but it does seem to be the same result as what is happening for you.
It might be possible that given our problems are similar but different, with the comparison of notes we could eliminate both problems.
UPDATE: I found that creating the worker unit based on the Wisp itself appears to trigger the same message that you have been encountering. As of yet, I don't know why it is doing that, but it does seem to be the same result as what is happening for you.
Last edited:
- Status
