Dungeon Master Forum

At a certain distance, I get fireball holes overhanging the edge of their wall. Is this something that is just held over from the original? (I cant believe I haven't seen it before)


dsb_text2map(0, 5, 5, 100, 1, {
"00000",
"00000",
"11110",
"00010",
"00000"} )
dsb_level_wallset(0, wallset.default ...

I tested unallocating the object definitions but it wound up crashing things.
So I'm guessing your put-them-in-an-unused-category approach is probably the best option

If there's a thread here for it then could I add requests for:

* a find an inst by ID number. At the moment I do a bunch of: find I need to know about inst #51342, load up the dungeon in a text editor and look up inst 51342 to get the coordinates, go back to ESB and go to those coordinates

* would ...

As an example, I have an extra row at the bottom of the cells.pcx like
https://i.ibb.co/Txd4GwYj/buttonkey.png

and modify the wallitem section of editor.lua


elseif (arch.type == "WALLITEM") then
if (arch.class ~= "DECO") then
if (arch.class == "ALCOVE") then
return (52+dir), 5
else ...

I put together a more concrete example:
startup.lua:

snd.doom = dsb_get_sound("sounds/doorslam")

function helmdarconpickup(self, id)
dsb_sound(snd.doom)
end

function helmdarctofrom(self, id, who)
dsb_sound(snd.doom)
end

objects.lua:

-- when picked up off ground
obj.helm_darc.on_click ...

Also, meant to ask one more, regarding sounds: is it possible to to play a sound when I put an object into the inventory or pick it up? Is there any example code as to do this?

I accidently replied to this without realizing that it was a page old. Then deleted the reply. Then realized I dont ...

Hmm. Played around a bit more, and now it seems to be working for me x_off and all?
where gfx/testbutton.pcx is a 12x12px test file

The doorbuttons use a custom draw method, you can see renderer_hack="DOORBUTTON" in the obj

I think part of that is ignoring the x offset

(But I'm guessing it also does a bunch of other stuff that you wont want to get rid of)

Set
gfx.doorbutton.x_off = 0
gfx.doorbutton.y_off = 0
initially

Rig up a test dungeon with a door and button and take a screenshot standing in right front of it
Measure how far you need to move the button image up and across.

Set
gfx.doorbutton.y_off
to -(how far you need to move the button up ...

Wouldnt you just put

gfx.doorbutton = dsb_get_bitmap("my_version_of_the_front_doorbutton_bitmap")
and
gfx.doorbutton_side = dsb_get_bitmap("my_version_of_the_side_doorbutton_bitmap")

in your gfx code?

Between system/sys_click_mouth, util/eatdrink and the consume_effect on a given object, there is a bit of a mismatch.

The consume_effect is called with the id of the object being consumed. But because food has an animation and thus a delay, the object is no longer valid by the time its consume ...

Thanks. I'll give it a try

Yeah it probably doesn't make too much sense to instruct monsters to head to a stairway when they aren't actually in the dungeon 8-)

...

Works for me now. Of course, only processing the monsters in the dungeon would also bypass the error anyway, so first I tried the dsb ...

Lua: 9425 @ 1 22 28 2
Lua: 9426 @ 1 22 28 1
Lua: 9427 @ 1 5 3 0
Lua: 9428 @ 1 25 5 0
Lua: 9430 @ -5 0 0 0
PROGRAM CRASH!
Yeah I'm thinking something doesn't work if the monster is in limbo?

edit It sometimes works in limbo too though, and I cant get my minimal version to crash by piling monsters ...

Tweaking my use_stairs code to

...
__log("ust")
local pz,px,py,pf = dsb_party_coords()
for monid in dsb_insts() do
local arch = dsb_find_arch(monid)
if (arch.type == "MONSTER") then
__log(tostring(monid))
end
if (arch.type == "MONSTER" and
dsb_ai_boss(monid) == monid) then
end
if ...

So I tried to make a simplified reproduction, but I'm not getting the same result. I'll see if I can reproduce it in the original dungeon next.

The following does **not** crash

dungeon.lua

---DSB ESB---
--[[ Autogenerated by ESB.
Trying to edit this file by hand may not give you
particularly ...

This was tweaked in the new version, so likely a regression there?

Reason: Segmentation Fault
Stack Dump:
DSBmain
DSBgameloop
dungeon_move
party_moveto
to_tile(on_trigger)
lua_call.member_func
lua.stairsdown.on_trigger
lua.dsb_ai_boss
monster_groupup

Oddly, the stairsdown.on_trigger I have doesn't ...

Thankyou again

(of course, I can tweak the base files in my own install, but better to have an upsteam fix for everyone)

Nice!

I had a minimal level where I was smooshing groups of critters together with dsb_move, but I hadn't been able to reproduce the issue...

Grasping at straws here:
What happens if we have monster group A+B and monster group C+D.
Then A+B split, where one of them moves to a new tile and onto a teleporter dropping them instantly into C+D.
Could A+B still be considered a group and one of them a boss long enough to cause some mishap? Or ...

Unfortunately, I cant see reproducing it as any more than random chance. There's nothing I can see that makes it likely here. The critters in question aren't particularly close to start with, and my last save was annoyingly old by the time it happened.

(0.81 for the record. I do a bit of AI tweaking for my stairs stuff, but I don't think anything that should be causing problems in the engine-side code...)

10165 is a level transition, several teleporters and a bunch of walking away from 10095 but its not impossible for them to have grouped up.

"Monsters cant agree who is boss
This is more than likely a bug in DSB"

log.txt:
AI: Boss 10165 thinks 10095 is boss!
AI: 10095 thinks 10095 is boss
Error: Monsters can't agree who is boss.
This is more than likely a bug in DSB.

uh, is that actually a disagreement?

It is now official: I have clicked the wrong start button too many times.


local front_door_noclick=3
function front_door_click(x, y, b)
if (b == 1) then
if (x > 488 and x < 512) then
if (y > 114 and y < 138) then
dsb_sound(snd.click)
-- dont start a new game unless we really mean it
if (gt ...

After one too many "this was technically solvable but there was a key under a trash pile about 5 levels ago you missed so now you're stuck", the overall plan is I'm looking at implementing an Oracle for that random dungeon generator I have.

My concept is a small permanent hit to a given character's ...

I knew messages were the proper way to do it, and I got things working pretty quickly once I stopped being lazy 8-)

But I figured I should find out the way it should behave and update the wiki. Now I get to be lazy there instead 8-)

The docs on the wiki imply a subrenderer would be called 6 times a second.

In actual use, it seems that a subrenderer will be called much faster for an item looked at via the eye than if put in the hand. Is this intended?

(I had thought I could use that 6 times a second for some idle activity, but ...

Cool. Like I implied I wasn't planning on using it but it having that side effect was wierd and unsettling...

Had another look around. What I had missed was that it only affects dsb_bitmap_textout with the MULTILINE flag set.

It still also breaks the main message area if you actually try to use it. But it wont affect most instances of dsb_bitmap_textout.

Oh, and if you try to use it to format the main ...

The way this works seems wierd?

It looks like it has global effects, so if I ever use it for formatting my own text, then the main system UI goes wonky?

dsb_bitmap_textout is used all over the system UI, but dsb_textformat is only used in the default subrenderer, so everything in the system is ...