Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add TS mobile EMP #20808

Merged
merged 2 commits into from Sep 9, 2023
Merged

Add TS mobile EMP #20808

merged 2 commits into from Sep 9, 2023

Conversation

PunkPun
Copy link
Member

@PunkPun PunkPun commented Apr 16, 2023

Depends on #20824

#19211

https://cnc.fandom.com/wiki/Mobile_EMP

This PR is still WIP, I need to figure out some stats such as the range of the EMP or how to make the MEPM not float

@PunkPun PunkPun force-pushed the mobile-emp branch 3 times, most recently from 2b9bc31 to 4f6ee4b Compare April 17, 2023 11:03
@PunkPun
Copy link
Member Author

PunkPun commented Apr 17, 2023

I'm thinking this of this structure.

Add 2 new traits

  • FireWeaponOnCondition
  • GrantConditionOnChargedDeploy

Then we could use them for these 3 units

  • MAD tank -> GrantConditionOnDeploy + FireWeaponOnCondition
  • Saboteur Added manual Saboteur cloaking #17823 -> GrantConditionOnChargedDeploy
  • Mobile EMP -> GrantConditionOnChargedDeploy + FireWeaponOnCondition

The difference between saboteur and memp is that for the latter the condition would activated for a long time, while for the former it would be for only one tick.

As for MAD tank, more logic will be need to be pushed out into other traits, it will likely need 2 FireWeaponOnDeploy traits for the 2 different interval weapons, it will need a trait for ejecting the driver and another for delayed self-destruction

@pchote
Copy link
Member

pchote commented Apr 17, 2023

Strongly disagree with the concept of a FireOnCondition trait. Conditions are states and shouldn't be used as events.

FireOnDeploy is the cleaner approach here (but maybe rename to FireWeaponOnDeploy to avoid confusion with it bursting into flame?)

@PunkPun
Copy link
Member Author

PunkPun commented Apr 17, 2023

Strongly disagree with the concept of a FireOnCondition trait. Conditions are states and shouldn't be used as events.

With MadTank as I described it would basically be a state. Repeatedly firing the weapon at a set interval until the condition is false.

@pchote
Copy link
Member

pchote commented Apr 17, 2023

That's describing something different, more like CashTrickler: the trait would be called e.g. FireWeapon with an Interval field, and just happen to be conditional.

@PunkPun
Copy link
Member Author

PunkPun commented Apr 17, 2023

Then I could just call it FireWeapon and just make it conditional

@Mailaender
Copy link
Member

The unit is hovering despite being a tank with tracks:
image
but I don't know how to fix that.

@PunkPun
Copy link
Member Author

PunkPun commented Sep 9, 2023

As I comment in the description. I'm not sure what the best way to fix it is, I assume something is wrong in voxel importing?

Applying a 1/4 of a cell offset to the body does fix it. Pushed a fix.

Screenshot 2023-09-09 at 17 14 12

@Mailaender Mailaender merged commit 4eb683a into OpenRA:bleed Sep 9, 2023
3 checks passed
@PunkPun PunkPun deleted the mobile-emp branch September 9, 2023 14:55
@Mailaender
Copy link
Member

Changelog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants