Difference between revisions of "Common Bugs"
→MoveTo on Containers
imported>Rangaro |
imported>Rangaro |
||
| Line 119: | Line 119: | ||
=== MoveTo on Containers === | === MoveTo on Containers === | ||
If you use MoveTo or PositionCell on a Container(a chest for instance), even if you update the world art of the Container using GetPos and SetPos, the collision information of the Container will not be updated. Example: If your script moves a chest to different positions inside a room, the chest will visibly move, but the player cannot open it. In order to open it, the player has to go to the chest's starting point. There the player cannot see a chest, but the chest's name will be displayed on the screen, and as soon as the name can be seen, the "invisible" chest can be opened. | If you use MoveTo or PositionCell on a Container(a chest for instance), even if you update the world art of the Container using GetPos and SetPos, the collision information of the Container will not be updated. Example: If your script moves a chest to different positions inside a room, the chest will visibly move, but the player cannot open it. In order to open it, the player has to go to the chest's starting point. There the player cannot see a chest, but the chest's name will be displayed on the screen, and as soon as the name can be seen, the "invisible" chest can be opened. | ||
As a workaround, you can create identical copies of the container, and then enable/disable them. In this case, a script should be attached to the container which handles the container's content. This is to ensure that each copy contains the same items at all times. | As a workaround, instead of moving one container around, you can create identical copies of the container, and then enable/disable them. In this case, a script should be attached to the container which handles the container's content. This is to ensure that each copy contains the same items at all times. | ||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||