Posted: Sat Sep 29, 2018 1:53 pm Post subject:
Hilarious bug with Slave Miners
Subject description: Dunno how vanilla reacts, but I doubt it's different.
Logic.exe was not found.
Also, I noticed Slaves would pop out of the GACNST spawned, tho only at high speeds, if the recordings are anything to go by.
The test map has no ore to speak of what-so-ever (it's completely blank).
_________________ One and only developer of the Command & Conquer Dune "C&C D" mod.
m7 wrote:
I tend to release things I create so that assets are never lost to hard drive problems, accidental deletion, or me having to pretend to care about rippers taking things from my project when it is done.
Last edited by TAK02 on Sun Sep 30, 2018 6:30 am; edited 1 time in total QUICK_EDIT
It has no UndeploysInto= so the only thing it can do is selling itself (Nothing appears after undeploying) when forced to undeploy
I don't think it's a bug.
If you try to let a unit/building born as a slaveminer deploy/undeploy to something else, some slaveminer properties persist _________________
Looks like a bug but not a bug at the same time, this is not logical when your own conyard undeploys itself into an mcv without your command for example _________________ If you are a MetalHead (Heavy Metal Fan) and don't want to be a metalhead, Just remove your metal ball from your head. �:p .
QUICK_EDIT
Looks like a bug but not a bug at the same time, this is not logical when your own conyard undeploys itself into an mcv without your command for example
Because it's initially a slaveminer. You already notice that when YAREFN converts to something else like SMIN it doesn't lose harvesting mission nor lose/renew any of its slaves. There should be some mechanism underneath to ensure the converter and the convertee behave as if they are one entity. So the AMCV shown in the video is technically a slaveminer but lack of slaveminer specific tags (guess the default values are used and it results “bizarre” behavior, plus there are no ores).
PS: you can make an auto-deploy/undeploy unit by making it a slaveminer and omit Buildup= to prevent selling _________________
Slaveminers will scan for ore, and when it find itself too far from the closest ore field it will undeploy into its vehicle form and move towards the ore field, deploy again.
This is how it is designed, so a building with slaveminer properties will follow this rule and undeploy itself, or to say, sell itself if it cannot undeploy into something. There are range scanning things specially set for them just as normal miners do, i.e SlaveMinerShortScan=. QUICK_EDIT
Do note that what I am worried about is not the selling happening.
What I am worried about is how the AMCV that ends up spawning is completely unusable.
Because of [GArEFN]UndeploysInto=AMCV
AMCV and GACNST are now both part of the slave miner logic, AFAI can see.
This explains the "I noticed Slaves would pop out of the GACNST spawned, tho only at high speeds".
The instant I deploy the AMCV that spawned via GAREFN undeploy, it starts the loop you see in the video.
THAT is the actual bug.
Not the undepoy turning into a sell order if there's no UndeploysInto defined. QUICK_EDIT
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum