Re: [NPC Pack] SMW Pokey
Posted: Sat Mar 07, 2020 10:31 am
You were never supposed to use it in NPC packs. You're supposed to use v.data. Looks like I typo'd ._basegame at the end out of habit in this case. Removing it should be simple enough. Though I don't know what would've changed that explicitly makes it so that subtable cannot be used for npc packs anymore at all.
You can simply find a sprite sheet for the snow pokey npc and reskin it over the npc already made....
However, there's this fix. Put this on the Pokey's lua.
Code: Select all
function pokeySMW.onNPCHarm(eventObj, v, killReason, culprit)
-- Ignore if wrong NPC or valid kill method
if v.id ~= npcID then return; end;
if killReason == HARM_TYPE_SPINJUMP then
eventObj.cancelled = true
return
end
local data = v.data._basegame
if data.adjacentAbove and data.adjacentAbove.isValid then
data.adjacentAbove.data._basegame.adjacentBelow = nil
end
end;Code: Select all
local data = v.data._basegamePerhaps you're doing something wrong. You can also ask for help at the Discord.

This error is entirely on your end and not present in the download in the first post. In line 46 you have invalid syntax.TheGameyFireBro105 wrote: ↑Tue Feb 02, 2021 12:19 pmThe issue just won't go away!
If it helps, here's my modified version of the files that I tried fixing myself, but to no avail:
https://www.mediafire.com/file/fqrkvjdw ... 9.lua/file
https://www.mediafire.com/file/qzyc9u1r ... 0.lua/file
this?Enjl wrote: ↑Tue Feb 02, 2021 1:02 pmThis error is entirely on your end and not present in the download in the first post. In line 46 you have invalid syntax.TheGameyFireBro105 wrote: ↑Tue Feb 02, 2021 12:19 pmThe issue just won't go away!
If it helps, here's my modified version of the files that I tried fixing myself, but to no avail:
https://www.mediafire.com/file/fqrkvjdw ... 9.lua/file
https://www.mediafire.com/file/qzyc9u1r ... 0.lua/file
You making more syntax errors. It's another instance where you have too many dots. If you encounter another error message after this, please actually like, read it. This is stuff that's glaringly obvious if you take a single look, even if you aren't familiar with lua. You are the one who edited these lines and introduced these mistakes, so it shouldn't be too hard for you to take a quick look at all the surrounding lines and see the inconsistency. You can see the line you need to edit this time in the error message. (The previous error message also showed which line was throwing the error, so by analyzing my previous response it should be fairly easy to derive where you can read the line in the error).