Official Legend of Grimrock Forums
http://mail.grimrock.net/forum/
Not at all, because the workaround would cause me too have to check hundreds of items several times every second just too make sure they aren't moved, and if you move it and place it outside the inventory the game will crash with the error that an item of that type already exist because the "bad object" work around.Lmaoboat wrote:I'm pretty sure onItemPickup working from the inventory would end up looking exactly that "ugly hideous literally Hitler" workaround you didn't want to use, anyway.
Thank you for the bug report! Unfortunately it's too late to fix these for the release but I'll add them to the bug list. Whenever we do an update we'll go through the bug list.Wolfrug wrote:I've got two crash-to-desktops to tell you about right off the bat, not sure how urgent they are but
I'm not completely sure what you're trying to do, but if your goal is to prevent the player from removing a certain item from inventory, I'm pretty sure that can be done with the scripting interface.Lilltiger wrote:Not at all, because the workaround would cause me too have to check hundreds of items several times every second just too make sure they aren't moved, and if you move it and place it outside the inventory the game will crash with the error that an item of that type already exist because the "bad object" work around.Lmaoboat wrote:I'm pretty sure onItemPickup working from the inventory would end up looking exactly that "ugly hideous literally Hitler" workaround you didn't want to use, anyway.
Trust me, I did try the workaround too see if I could make it work, but was way too buggy.
Code: Select all
skull = spawn("skull")
party:getChampion(1):insertItem(31, skull)
function slotcheck()
if getMouseItem() == skull then
setMouseItem(null)
party:getChampion(1):insertItem(31, skull)
end
if party:getChampion(1):getItem(31) ~= skull then
setMouseItem(party:getChampion(1):getItem(31))
party:getChampion(1):removeItem(31)
party:getChampion(1):insertItem(31, skull)
end
end
I completely replace the inventory with other items that fills all the slots, and non of these items should not be allowed to be swapped with another, but indeed if it is guarented to check it every frame it might be possible to do it. So a timer that activates evry 0.005 should be 200hz right?petri wrote:I'm not completely sure what you're trying to do, but if your goal is to prevent the player from removing a certain item from inventory, I'm pretty sure that can be done with the scripting interface.Lilltiger wrote:Not at all, because the workaround would cause me too have to check hundreds of items several times every second just too make sure they aren't moved, and if you move it and place it outside the inventory the game will crash with the error that an item of that type already exist because the "bad object" work around.Lmaoboat wrote:I'm pretty sure onItemPickup working from the inventory would end up looking exactly that "ugly hideous literally Hitler" workaround you didn't want to use, anyway.
Trust me, I did try the workaround too see if I could make it work, but was way too buggy.
First check every frame where the "cursed" item is in the inventory and mark the champion index and inventory slot if the item is found. Then check if the mouse item contains the cursed item. If it contains remove it from mouse item by calling setMouseItem(nil) and place it back into the inventory slot. Just create a timer that runs at very high frequency (e.g. 200hz) - this should guarantee that the code is executed every frame.
If you're worried about performance, don't be. The game engine, which is written in Lua, updates every object in the current level each frame and other levels at a somewhat slower pace - that's a lot of updates - and we don't have any performance problems even on slower computers.
)