ztz2019

I don't know why but still no use

Congratulations

Could you explain it more clearly? Is SWAPPING_TO_WEAPONSET_1/2/3 in modelstate? And is any codes for example?

I could just make 2 weapons which the new one is "fake deploy" that firing without deploy needed and preattackdelay=3.5s and have an "deploying" anim, so it looks likev unpacking to fire but in fact it's just normal firing like tanks without unpacking. But I still want to realize the true 2 firing mode with real deploy function like CC2 artillery and juggernaught.

Since spectre and Juggernaught always make themselves into dangerous place to get better shooting range, I tried to make them become immobile firebase and succeeded in meeting expectation. I just change DeployStyleAIUpdate into normal AIUpdate and add corresponding SP/Upgrade/Attr... with unpacking and packing buttons and so on. However, I want to let this kind of unit can both be mobile siege unit just like original game when meet with sudden enemy situation and immobile firebase by manual operation. So I returned AIUpdate to DeployStyleAIUpdate, and it went wrong no doubt. It will unpacking to deploy status after I click the unpacking button, the unit looks also in deploy model state. But it will unpack again when it is about to fire. And also it will pack twice, one for packing button, one for the true packing function itself. So what should I do? I want it autonomously unpacking to immediately firing as original game and manual operation to be immobile firebase if I click button and won't unpacking or packing twice. And I uploaded the code which can be compiled by Wrathed. testmod.zip

I may repeat my problem to let others understood. Now the KW/TW original set is if a unit contains 2 weapons, it will just move to the longer range weapon's range and stop to fire, so the shorter range weapon is unused. I need a kind of weapon or unit set, that when the unit contains two different range weapons, 1 for long weapon range, the other for short range, and though target is get in longrange weapon, it will still run to short one's range, so both 2 weapons could fire normally.

There's another problem which if be solved may helpful to the first issue, that's how to truely remake ZH's overlord modularization upgrade. Now most of CC3/KW mod which try to realize Overlord sub turret upgrade function is in fact using unit's own weapon and model, by using the upgrade to show the hidden sub obj. and active the sub weapon. The ZH's overlord modularization upgrade is adding independent sub unit like spawned slave in KW such as repairing drone and invader fighter, but I always can't realize a totally same turret. If Overlord upgrade could be realized, the first issue can be solved, too. I can using sub turret with longrange and parent unit has shortrange weapon.

In fact my 1.08 gamma never compiled succeed even once time.

Supposing a unit who has a longrange weapon, and it will approach the target to let weapon fire as usual(its VisionRange is longer than weapon range). Now I need the unit still be approaching to the target until it can get in touch with( or contact with? Don't mind my grammar) it. Once I tried to add a very short range dummy weapon and attempt it will run to target, but it stopped when the longrange weapon can open fire, never go further.

May the Dickman bless you.

Thx a lot, it's very useful.

I tried to add FireWeaponUpdate for a KW unit to reproduce microwave tank's BBQ circle, it works well when MW tank is static, but invalid when it moves. It's not weapon itself's problem since I already set CanFireWhileMoving="true". So anyone noticed this phenomenon?

Well, I fixed this bug, it's not bug, only give TIbfield's model an OBBox to make it selectable is enough.

I still can't realize this function, I tried to research TibHive's code, but I could just let ocl suddenly appears on TibField , can't wait until Cmdo approaching to it to build up. It seems I need to explain it more clearly, the function I need is like building a bunker on TibField, it needs unit choose target (to TIbfield) then come up to TibField and begin to build the structure on Tibfield.

I still can't realize the ocl on TibField, so I put on my code to anyone learning to fix it, thanks any how. Please try to realize one unit can build/dig/ocl sth. on TibField, thanks again. Data.7z