Open door by placing gem on plate or on point of map

[Dinasty]

Hi,

can someone give me the lua script to open a door by placing a gem on a specific tile of the map? (without using alcove or altar)

Code: Select all

function itemCheck()
  for item in map:entitiesAt(15, 14) do
    if item.id == "red_gem_1" then
      dungeon_secret_door_1.door:open()
    end
  end
end

I tryed this but doens't work

[Duncan1246]

Hi,

can someone give me the lua script to open a door by placing a gem on a specific tile of the map? (without using alcove or altar)

Code: Select all

function itemCheck()
  for item in map:entitiesAt(15, 14) do
    if item.id == "red_gem_1" then
      dungeon_secret_door_1.door:open()
    end
  end
end

I tryed this but doens't work

Hi, Dinasty,
Try party.map:entitiesAt(15,14) , it should work
Duncan

[minmay]

surely you want self.go.map or dungeon_secret_door_1.map, not party.map

[Duncan1246]

surely you want self.go.map or dungeon_secret_door_1.map, not party.map

Hi Minmay,
What difference does it make?

[Dinasty]

self.go.map
dungeon_secret_door_1.map
party.map

all of theese works, thank you

[AndakRainor]

With dungeon_secret_door_1.map you will be sure to test the map in which the door is included. party.map will give you any map where the party currently is, self.go.map any map where the item is, or worst, a nil value if it is not on any map (inventory, container...).

[Isaac]

self.go.map
dungeon_secret_door_1.map
party.map

all of theese works, thank you

What difference does it make?

It is that party.map is always the current level; [where the party object is]; self.go.map (and dungeon_secret_door_1.map) might not be [it's whatever level the object is on]. So if a script runs while the player is on a different floor than expected (or assumed), then that script can potentially use the wrong map.

If Dinasty's script used party.map, and the party were to drop the item through a pit onto the tile below, then it would fail to detect, because that script would then check for the object on the party's level ( one or more floors above ~in the tile where the pit is). If the party isn't on that level, or leaves the level before the test is performed, then it will not check the correct tile. If the check is on a slow timer, the player might be able to use a pit, teleporter, or a stairway before the itemCheck() test.

**Also: If dungeon_secret_door_1 (or any other object used for its map location) is destroyed, that reference in the script becomes nil; that's something to bear in mind when using it.
The party.map, and self.go.map references never become nil for an active script.

[Duncan1246]

Thanks Andak Raynor and Isaac. This confirms to me that the difference is useful only in limit situations as that quoted by Isaac.

[Isaac]

Using party.map is generally safe for instant [or trivial] access to the current map when called. The problems can come when one assumes the party's position is on the expected map when the script is run. So if your script relies on timers and/or floor_triggers that aren't activated only by the party, then a more reliable map reference should be used, unless you have a specific reason that the script should always use the party's map location for its actions.

Also... in the case of script_entities: Some use their object's position on the map as a basis for variable coordinates. In this case using self.go will the change if the script if object is moved, (or copied & pasted somewhere else).