Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • solarus solarus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 229
    • Issues 229
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Solarus Games
  • solarussolarus
  • Issues
  • #1233
Closed
Open
Created Jul 27, 2018 by Diarandor@DiarandorDeveloper

Add events for carried entities

Add events:

  1. "carried_object:on_carried()", or even better, "carried_object:on_carried_by(other_entity)". This may allow some entities to escape from the hands of the hero (or an enemy) when he carries them, for instance.

  2. "carried_object:on_thrown()", or even better, "carried_object:on_thrown_by(other_entity)". When this event is defined the "built-in thrown movement" should not happen. The devs of the game should code what happens then, including the falling trajectory. When the event is called, the entity is not being carried anymore.

  3. "carried_object:on_fallen()", called when this entity has fallen to the ground after being thrown. This may be use to code entities that bounce on the ground, or NPCs/enemies that are restarted when thrown, and many other things (we can think more uses later).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking