raocow's talkhaus

Kevsoft wrote:Layers in SMBX don't have positions. They only move their objects by the speed, nothing else.

TiKi wrote:Hey Hoeloe could you please make something like the RaoCoin counter but for red coins? That doesn't store anything (a la shop) except for displaying the level's amount you collected? A friend of mine wanted that.

local raocoins = 0;
local lastRaocoins = -1;

function onLoop()
	local rcs = findnpcs(274, -1);  --find all raocoins
	local raocounter = 0;
	  
	  for key,value in pairs(rcs) do
		raocounter = raocounter + 1; --count the number of raocoins
	  end
	  
	  if(raocounter < lastRaocoins) then --if there are fewer raocoins this frame than the previous frame
			raocoins = raocoins+lastRaocoins-raocounter; --take the difference between the two and add that to the counter
		end
	  lastRaocoins = raocounter; --keep track of the raocoins on the previous frame
end

Kevsoft wrote:The new Animation/Effect System in the upcoming LunaLua version:

Kevsoft wrote:The new Animation/Effect System in the upcoming LunaLua version:

// 0x+44	w	= Activated / interacted with player flag

Rockythechao wrote: Also, I just remembered that NPCs have an offset for checking whether they're interacting with the player.

Hoeloe wrote:Oh, also, Kevsoft, this has been bugging me a little for a while, but you keep using the word "documentary" when you mean "documentation". A documentary is a non-fiction TV or radio program, while documentation is a record of information about a programming language or API.

function isCrabDead() return findnpcs(209, -1)[0] == nil end

function onLoop()
	if not isCrabDead() then return end
	local myBlocks = blocks()
	local plScreen = player.screen
	local k = 0
	for _,v in pairs(myBlocks) do
		k = k + 1
		local curX = v.x
		local curY = v.y
		if(k % math.random(1,2000) == 0)then
			if(player.y-plScreen.top < curY and player.y-plScreen.top+600 > curY and player.x-plScreen.left < curX and player.x-plScreen.left+800 > curX)then
				runAnimation(108, curX, curY+16, 1065353216)
			end
		end

	end
	earthquake(5)
end

Kevsoft wrote: PS: I feel LunaLua is already quite finished and I want do now more work on Wohlstand's Editor. I only did LunaLua that you guys can do awesome stuff with LunaDLL, but I still stick more to the Editor than to Lunadll.

Hoeloe wrote:There are still quite a few things missing. Custom cheats, for one, and there are a few things such as disabling player input which still need to be worked out.

Hoeloe wrote:So does the levelEnd function just end the level as though you've encountered an exit?

Kevsoft wrote: I didn't say I am completly finished, I just said that I am going to slowly "close" this project.

Kevsoft wrote: "exitLevel()" does simply end the level immediately.

Hoeloe wrote:Okay. Have you released the source anywhere so others can continue it when you do?

Hoeloe wrote:Okay. I can see that being quite useful for a joke I have planned.

Rockythechao wrote:The link to the source code has been at the bottom of the original post for quite a while, I've been reading through it to try and figure out stuff myself. It's pretty easy to miss down there, so you might want to move it up to the where the links for the download & documentation are.

Rockythechao wrote:It's understandable if you want to move on, Kev. We really appreciate all of the effort you've put into this module :D
I've been set up to work with the source for over a month now, kept meaning to mention that but I don't think I ever did... And now my trial for Visual Studio's probably expired so I'll have to get a full license.

Rockythechao wrote:And on that note, are the NPC constants I put together going be implemented? I don't mean to be pushy about it or anything, it's just that I haven't gotten any feedback on those things so I don't know if anyone's even interested

Kevsoft wrote:Sorry about that I missed that. I did see it but I thought you implement it as a softcoded API part. I can surely do that for the hardcoded part in the dll itself.

• Custom context-sensitive NPC icons that can be displayed from further away than the SMBX default; you'll know whether the NPC is friendly or an enemy the moment the appear onscreen, and you'll know whether that NPC has anything new to say or to differentiate between flavor/advice NPCs and quest-givers
• Call cinematX coroutines by talking to NPCs -- complex cutscenes, shop interfaces, etc.
• Wrapping regular NPC dialogue in cinematX messages to keep it from interrupting LunaDLL/LunaLua stuff

Kevsoft wrote: Sorry about that I missed that. I did see it but I thought you implement it as a softcoded API part. I can surely do that for the hardcoded part in the dll itself.

NPC_ID_GOOPA

NPCID.GOOPA

Hoeloe wrote:

Kevsoft wrote: Sorry about that I missed that. I did see it but I thought you implement it as a softcoded API part. I can surely do that for the hardcoded part in the dll itself.

The constants would be best softcoded in my opinion, since Lua has a global namespace you can use, they can just be put into that. It might be best to have them as part of a subtable, though...

Rockythechao wrote:Changing the NPC's message pointer does indeed disable the speaking interaction in-game!

NPCID.1UP_SMB = 186

Kevsoft wrote:

Rockythechao wrote:Changing the NPC's message pointer does indeed disable the speaking interaction in-game!

Do you mean changing the text or changing the pointer value itself?
Because if you mean the text then it would be strange... I used the API part (for example NPC.msg.str = "A text") and it works perfect.

cinematX.npcMessageNPCs = {}
cinematX.npcMessagePointers = {}
cinematX.npcMessageStrings = {}

Edit:
Your name API is not working out that well.

Code: Select all

NPCID.1UP_SMB = 186

is not working because the key-variable is starting with a number instead of a letter.