Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • solarus solarus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 222
    • Issues 222
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Solarus Games
  • solarussolarus
  • Issues
  • #819

Closed
Open
Created Jan 04, 2016 by Diarandor@DiarandorDeveloper

Add property to destinations to ease saving starting position

It would be useful, specially for the Editor, to have a property "save_starting" for destination entities. This variable could take the three following values:

  1. "changing_world" (or nil). This should be the default value (to keep compatibility with the current engine and editor properties) and would update the starting position of the hero if and only if we are changing world when arriving to this destination.
  2. "always" (or true). This will always update the starting position when arriving to this destination.
  3. "never" (or false). This will never update the starting position when arriving to this destination.

Also we would need getter and setter functions to get and modify the value (from the map script) of this property of a given destination.

If you decide to add this customization property, do not forget to add this property to the Editor, which will be very useful for quest makers. (If you agree with this request, we should open an issue for the Editor too.)

EDIT: I am not sure if I will use this feature, so it's fine if you close this request it if you think it's not necessary.

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