-
-
Notifications
You must be signed in to change notification settings - Fork 668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
floor in entrance of poi is not allowed to walk on it #3144
Comments
Have a same problem |
IglaOTS_40qGwVdmSL.mp4yup same problem |
This issue occurs when a walkable tile (e.g., grass, dirt, pavement, sandstone) is spawned above a non-walkable tile (e.g., lava, shallow water). I tested this by creating (spawning) these items as a GOD using the /i command and placing a walkable item above non-walkable spots. Example: cant-walk-floor.mp4 |
@Regeton5306
for i = 1, #lava do
Game.createItem(5815, 1, lava[i])
end with this: for i = 1, #lava do
local lavaTile = Tile(lava[i]):getItemById(21477)
if lavaTile then
lavaTile:transform(5815)
end
end When using Tile::transform() it works well to solve poi entrance. |
Tested the fix for POI from Jeansouzak and it works IglaOTStest_dmQuIC16qP.mp4 |
…iabr#3196) Implements an alternative solution to handle lava tiles in The Pits of Inferno Quest. The logic in register_actions.lua has been modified to transform existing lava items (ID: 21477) into the floor item (ID: 5815) using Tile:getItemById and Item:transform, instead of relying on Game.createItem. This addresses an issue where lava tiles in The Pits of Inferno Quest were not behaving as expected Resolves opentibiabr#3144
Priority
Medium
Area
What happened?
When using the pickaxe on the stone, the floor is created but it does not let you pass, you just bounce and it tells you there is not enough room and in the console an error message appears [combatTypeToIndex] Combat type 255 is out of range, called line '2480:54' in 'bool __cdecl Monster::isImmune(enum CombatType_t) const'
What OS are you seeing the problem on?
Windows
Code of Conduct
The text was updated successfully, but these errors were encountered: