Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicDungeons MythicDungeons
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicDungeonsMythicDungeons
  • Issues
  • #522

Closed
Open
Created Jun 19, 2025 by Forgettings@Forgettings

[Bug] Procedural Dungeons, Block Movement and Teleport

Due to the inputs for both of these functions, requiring a coordinate location in the world. The functions do not work as intended. Since Procedurally generating the dungeon changes the locations of the blocks or rooms in a way that the user can not anticipate there is no way to successfully utilize these functions.

For example if you want to animate a door opening you would have the blocks move down or up, but the required argument needs a world location and so the blocks begin to move towards the location programmed in the edit world which is no longer relatively speaking in the same place as in the room.

To fix this, the end location would need to be in relation to the blocks starting position so that wherever the block starts the correct path can be created to the correct relative location in the room it is being summoned to.

As for teleport, it also does not work and teleporting should be not based on the exact coordinates in the world but instead to the location relative to the block in the room.

Edited Jun 19, 2025 by Forgettings
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking