Carryable: ignores Conditions under specific circumstances
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 17.4k
- Forks
- 3k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 14
Description
When a unit has WithSpriteBody: & WithFacingSpriteBody: , alongside GrantConditionOnDeploy: & Carryable:
The Carryable: trait ignores any conditions given to the unit & defaults to WithSpriteBody over WithFacingSpriteBody.
Easy repo:
- Add the following to any vehicle in RA, I used MRJ & added RequiresCondition: deployed to the spinner.
GrantCondition@AlwaysActive:
Condition: alwaysactive
WithFacingSpriteBody:
RequiresCondition: undeployed
Name: bodymove
WithSpriteBody@deployed:
Sequence: idle
RequiresCondition: !undeployed && alwaysactive
Carryable:
LocalOffset: 0,0,200
GrantConditionOnDeploy:
DeployedCondition: deployed
UndeployedCondition: undeployed
Facing: 0
AllowedTerrainTypes: Clear, Road, Rough
UndeployOnMove: true
UndeployOnPickup: true
- Add the Carryall trait to the Transport heli:
Carryall:
BeforeLoadDelay: 10
BeforeUnloadDelay: 15
LocalOffset: 0, 0, -128
AllowDropOff: True
This will result in:

This is because alwaysactive is not granted to the unit when it is picked up.
If you delete:
GrantCondition@AlwaysActive:
Condition: alwaysactive
It will be the same, except this time it will render WithSpriteBody@deployed: & not WithFacingSpriteBody:, because undeployed has not been granted.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with the MRJ and Transport heli configuration described in the report, including GrantConditionOnDeploy, Carryable, Carryall, WithFacingSpriteBody, and WithSpriteBody. Trace how pickup affects conditions and sprite-body selection. Done means carried units retain the relevant conditions and select the expected sprite body in both deployed and undeployed states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100