Dungeon Master Forum

They're both still being drawn. The problem is the order is no longer defined, and it seems to draw Ya-Ir on top, which completely obscures Ful-Bro-Neta. I'll specify the draw order in 0.79. (By the way, the underlying C code hardly changed at all. The table stuff is all implemented in Lua, and is r...

GorCoin is a brand new cryptocurrency that you can mine right from inside DSB at the same time as you play! It's not like the game itself actually puts your GPU to use, so why not use it for something? In case you've been out of the loop, cryptocurrency's ability to both make transactions much easie...

In ESB, under ESB Options, there is a checkbox for "End game if whole party removed." If the box is unchecked and the entire party is removed, you will revert to ghost mode. If it is checked, you'll go to the "The End" screen. (As of 0.79 it's impossible to select a dead characte...

Now I almost feel bad about fixing this.

My development PC runs Windows 10 so it should work fine!

I can't reproduce that. What exactly were you doing? What error is produced when it crashes?

No, not really. In standard Lua you'd use os.date or os.time but DSB doesn't enable the OS or IO libraries for security reasons.

Solved it! In DSB 0.79+, if you return true from sys_render_other , then the currently rendered UI bitmap will be given top priority for that frame, which will allow objzones on that bitmap to work even if it's overlaying a dungeon clickzone. That should allow your objzone-based pop up chest interfa...

Ok, I see what's going on. Standard DSB doesn't respond to a clickable flooritem in the same tile as the party, because that normally just never happens, so the click is always just sent to the standard clickzone for dropping items on the floor instead. If you click the flooritem outside of that zon...

There aren't multiple UI elements, it's all very discrete. I was talking specifically about objzones, and how you have gui_info.stats , gui_info.inventory , gui_info.poisoned , and gui_info.dungeon_overlay all defined and taking up the same space on the screen. Only one of these will receive clicks...

Objzone clickzones in the main viewport have a couple of significant problems due to the way DSB handles clickzones. DSB creates all of the necessary clickzones for the game's UI, and also creates big "meta-clickzones" for any UI elements rendered by Lua. The Lua code (either the base code...

That isn't how they're "supposed" to work so your mileage may vary.

If you return true from the arch's on_click function, then DSB won't allow the item to be picked up. This may work for you, but remember that to DSB it's still an item, so it'll still activate triggers, get grabbed by teleporters, and other things you may not want a decoration to do.

If you've invoked DSB via ESB, you can move the "current position" around in ESB and your position in DSB will jump around accordingly.

Ok, thanks, I could reproduce it this time and it was actually a symptom of a pretty serious problem with the message queues. I've replaced the DSB 0.78 download, so please download it again to get the fix. Your old code should work fine now.

I just tested, and multidraw wallitems can still send destroy messages to other multidraw wallitems on the same tile, and the targeted item is indeed destroyed. So I'm not sure what was going wrong but it's not that. So, yeah, I don't know either. Let me know if you run into a reproducible issue, th...

You need to dsb_bitmap_clear_alpha the bitmap to assert that you want to use an alpha channel and what the base alpha value for unmodified pixels should be. It worked before because DSB tried to be "smart," but as you saw, sometimes it made the wrong assumptions and everything got messed u...

I don't know what you mean by that. The only thing I changed was how multidraw wallitems handle clickzones.

Yes, dsb_get_alt_wallset.

If you're using 0.78 and up, if you change bitmap_clear_alpha to wrap dsb_bitmap_clear_alpha your code shouldn't need any modification.

What's new: - Added on_see_party event when a monster spots the party - Added on_frighten event when a monster is scared away - Added support for custom damage types to be shown via damage popup - Added other_side graphics for flooritems and flooruprights - Added volume control (via vol exvar) to am...

Ok, I figured out what was up with your images. DSB creates the hole in the wall by first drawing the wall to a separate bitmap, and then it draws the hole onto the wall. Transparent pixels in the hole are masked via whatever means the image uses-- in DM, this is color index 0 for an 8-bit image, bu...

The edge weirdness is because your image is a nonstandard size and DSB isn't accounting for that. I'll fix that.

The black not being transparent and the hole not being created in the wall seems like there's something wrong with your images. Are they included in the archive you sent me?

It uses a 4 bit bitmap because it's straight from DM, but you can use an 8 bit bitmap also and it'll still work. Color 0 is the transparent portion and power pink is the "hole" in the wall. As noted above, this means there's no support for alpha channels. DM's graphics don't need it, and i...

When DSB is in "draw one wallitem per wall" mode, a click on any wallitem propagates click messages to any other wallitems on the same wall. Normally that's what you want, but if you're using multidraw , then you have two wallitems (and thus two clickzones) being drawn, so the weirdness yo...

In your call to dsb_make_wallset_ext pass a table including the two bitmaps rather than the single "hole" bitmap. The first entry in the table is the hole, the second is the glow to add to the viewport.

Ok, so! Two things! First, the text had so many problems because text was always drawn with an alpha of 0. This isn't a problem with powerpink-based bitmaps (since alpha is ignored) but of course it causes problems if you're trying to draw onto a bitmap with alpha channels. Allegro 4 unfortunately c...

I don't know either! Can you send me your dungeon?

If something needs to be fixed I'd rather be able to include the fix in 0.78.

I didn't change dsb_current_inventory and it works fine for me, so something else must be wrong. I tested with both the 0.78 WIP and the distributed version of DSB 0.77 and they both worked fine.

Can you be more specific what "stopped working" entails?

Also, are you adding to the info tables or have you completely redefined them?