Grimrock

Grimfan wrote:Is it safe to use player.level when spawning objects (and particles, items, etc) for local functions. I find having to go back and change the spawn level whenever I add a new level to my dungeon tedious.

Isaac wrote:

Grimfan wrote:Is it safe to use player.level when spawning objects (and particles, items, etc) for local functions. I find having to go back and change the spawn level whenever I add a new level to my dungeon tedious.

The object/variable player.level doesn't exist in the default game. If you mean party.level, you can safely use it, but it changes to whatever level the party is currently on. So it's only useful if what you want to spawn must always appear on the same level as the party. If you use it to spawn objects on different floors it won't work if the party isn't on that floor when the objects are spawned; the objects will appear on whatever lever the party is exploring (and could be inside or outside the level's walls).

Grimfan wrote:Also, most of the spawns I'm talking about are initiated by the player when they step on a floortrigger or pull on a lever, so that means I am good to go (unless someone can point out another big pitfall).

Grimfan wrote:What if I want to have them press the same button twice in a row or go back to a previous button and press it again?

--button lock with combination
B_table = { --=====================[Add all of your button id's here. Put the number of presses in the braces {#} ]
			wall_button_1 = {3},
			wall_button_2 = {1},
			wall_button_3 = {2},
			
		  } --======================[]
for _,each in pairs(B_table) do each[2]=0 end 	--sets the recorded number of presses to zero.
previous_button = ""						--stores the last button pressed

function buttonCapture(button) 			
	if button.go.id ~= previous_button then		--runs code only if it's a different button.
		previous_button = button.go.id			--sets the current button as the previous one. 
		B_table[button.go.id][2] = 1			--resets button values
		B_table[button.go.id][3] = false
		if B_table[button.go.id][2]>B_table[button.go.id][1] then		 --catches too many presses; clears all previously correct button values. 
			for _,each in pairs(B_table) do
			 each[2]=0 each[3]=false
			end
		end	 
	end
	
	if B_table[button.go.id][2]>B_table[button.go.id][1] then			--catches too many presses; clears all previously correct button values.			
		for _,each in pairs(B_table) do each[2]=0 each[3]=false end 
	end
	 
	if B_table[button.go.id][1] == B_table[button.go.id][2] then		--detects correct number of presses.
		B_table[button.go.id][3] = true							--sets the button entry to true
	 else B_table[button.go.id][3] = false							--or false if incorrect
	end
	B_table[button.go.id][2] = B_table[button.go.id][2]+1			--increments the recorded number of button presses
	
	local unlock = true
	for _,b in pairs(B_table) do
		unlock = unlock and b[3]								--compares all buttons for true values; results in either unlock == true or false
	end
	
	if unlock then
		
		--=====================================[success, put unlock logic here]
		
		dungeon_door_iron_1.door:open()
		
		--====================================================[]
	end
end

THOM wrote:Is there a way to alter during the game a monsters brain behaviour?

I tried this but all I got was "attemped to call method 'goTo' (a nil value)" :

Code: Select all

ghost_1.brain:onThink(self:goTo("dungeon_floor_1"))

PedroMoniz wrote:There is a font(font) but what exactly is a font for the game?

MrChoke wrote:

THOM wrote:Is there a way to alter during the game a monsters brain behaviour?

I tried this but all I got was "attemped to call method 'goTo' (a nil value)" :

Code: Select all

ghost_1.brain:onThink(self:goTo("dungeon_floor_1"))

Yes, it is very moddable. I am doing extensively in my mod. First though, it's a hook. It seems you are calling it almost like a regular function call. You add the hook either directly in the "defineObject" asset if you are making a custom monster or you use "addConnector" to add the hook to a built-in monster. It's giving you that error because "self" in that context is not the Brain component. It's probably the script component.

Regarding the goTo function, it is a valid function that you can call on the brain. However, the string you use must be an item, not the name of a floor. Something lke "prison_key_1" or whatever.