Bug - shifts when echoed to a different location still spawn eggs in original location
d0ped0g
Join Date: 2003-05-25 Member: 16679Members
Join Date: 2003-05-25 Member: 16679Members
If you evolve echo on a shift, echo it to another location, and spawn eggs, it will spawn eggs in the original location where you first dropped the shift. I have not tried to see what happens once the infestation has receded on the old location.
Presumably, eggs should still spawn around the shift, even if it has been echoed somewhere else.
Presumably, eggs should still spawn around the shift, even if it has been echoed somewhere else.
Comments
^_-
Just tested and yes as long as the infestation is there you can keep spawning eggs. But once the infestation is gone, the eggs spawn next to where ever you moved the shift to.
Exploiters.
Exploiters.<!--QuoteEnd--></div><!--QuoteEEnd-->
Chances are the shift just died and there were still eggs remaining. It's rare that a comm will get a echo shift (at least I don't see it very often in pubs).
And yeah right exploiters.. Frankly, I retain the right to be able to echo my shift and still retain the egg spawning function, even if it's not working quite as intended, without it being referred to as an exploit. Am I supposed to stop spawning eggs because there's a bug? Shouldn't have to choose between echoing my shift and spawning eggs.
To be honest, the bug works against you. If I wanna echo my shift outside a location somebody's attacking and spawn eggs there, I can't, because they just spawn back where it was before :/
This would cost 15 (shift hive) + 10 (shift) + 15 (evolve echo) + 10 (eggs) + 5 (echo shift back to base) = 55 res
And every time you echo the shift back to the location to spawn more eggs and echo back again it would cost 10 res + the resources you spend on the eggs.
I don't see it being that viable a strategy to be honest, even if you only echo back the shift when it gets under fire...