Dungeon Master Forum

How many bitmaps are there? Giving each bitmap its own frame counter would be sort of a mess, which is why I currently use a global frame counter for things not associated with an object inst. However, as long as you only have a few different instances, or they're going to be synchronized, I could j...

It does already exist. It's dsb_mouse_override (bmp), and takes the image you want to use. Pass it nil or false to remove the override image. Where is the animation? If the animated bitmap is associated with an inst, you can use dsb_set_animtimer (inst, timer_val) to reset the timer to 0. Other anim...

If the dungeon is compiled, DSB will refuse to load a dungeon compiled with a newer version.

The C code doesn't know about the monster_level_info table; it just calls sys_monster_enter_level and the rest is handled with Lua code. So from that stack trace I don't really see a connection to monster_level_info but clearly something isn't working right. At this point I don't know if it's someth...

I could add this, but I don't really like the idea of version-locking a dungeon to a particular version of DSB. I try to maintain backward compatibility and I think I've done pretty well since about 0.60 or so. Being realistic about it, given my rather slow pace of DSB innovation, the biggest change...

If there's only 1 party member then we're basically back to the issues from earlier in the thread. Unless you want spin dodging to be a thing, the code in the engine that handles collisions would have to be modified. That's not that hard to do but it would require modifications to the supporting Lua...

Like any monster, they can't attack the back row (unless they are specifically allowed to do that, like materializers) if there is a party member in front. This means there will be some issues if you use "dummy" party members, which will exist regardless of whether you make all monsters si...

It'll be a bit hacky but it could possibly work. I guess you could disable the marching order widget but randomly change the marching order around in code so missiles would come from either side.

The main remaining issue will be in the targeting of monsters' melee attacks, I think.

Right, I don't maintain the magic map code, so I really have no idea about how it works.

Yeah, it applies to leveling up only. Stats that are above/below their maximum are only shown in red or green until they're back to the normal maximum value.

It may not be the best approach but I should note that the stat being shown in red after an increase to the maximum value is also what DM does.

Just to clarify how all these numbers fit together, for normal monster movement, its act_rate is the number of ticks in between turns. When it has attacked, the attack_delay is also applied. This slows down wasps and the like (early versions of DSB didn't have this, and you got stung to death quite ...

It modifies how DSB's image scaling code works so it applies to anything that gets scaled before it is drawn. This is most commonly objects in the dungeon view, but you can also scale bitmaps yourself via dsb_bitmap_blit. Bitmaps that are drawn at their normal size aren't affected at all.

I also like the idea of a new custom dungeon with your redone updated graphics. I will show my support by providing something at the engine level to do the sort of scaling you want; check the DSB subforum. Although I do feel sort of good that DSB is flexible enough this could be solved by the dungeo...

DSB 0.80 will include dsb_lores_scaling , which takes a boolean parameter and, when enabled, tells DSB's scaling code to scale everything to 50% of the specified size and then scale it back up, so distant objects have a more authentic DM low resolution look. Ideally it's something you'll set and for...

For what it's worth, I thought your additions to the DM mechanics were quite nice, and to see them in a new dungeon would be pretty great.

What glitches are you talking about with DSB, though? And what are you doing to generate a "proper old-school low-res view"?

I wouldn't necessarily say "abandoned" but I'll certainly admit that I haven't been able to work on DSB lately.

After the new year I should be able to get back to DSB and I can (finally) get a new version out.

Unfortunately it seems like it was not.

This could probably be useful, but it's probably a somewhat major addition-- if nothing else, it's a decent amount of typing for me. It would also likely be tricky to get everything working properly, especially for Things. I'll keep it on the back burner but it's not the sort of thing I can really d...

This is strange but not unexpected. Unfortunately, it's a pretty experimental feature that I admittedly don't have the resources (or the time) to debug to the point where it's trustworthy, especially since DSB wasn't really initially created with a fully interactive editor in mind. It's fun when it ...

Just for the record I still haven't been able to reproduce anything like this unfortunately.

This isn't "supposed" to happen, as ESB does attempt to clean up after itself, so if you have some specific instructions how to reproduce an issue I can take a closer look at it.

I don't think so.

What were you doing to cause this?

What's new: - Increased the number of possible user-defined UI zones from 5 to 15 - Added ability to prioritize sys_render_other clickzones - Added ability to specify draw order of conditions - Fixed handling of drawing objzone graphics on bitmaps with alpha - Fixed a crash when pulling an inst out ...

Ok, I thought I wasn't going to fix this, because it won't ever come about during normal play, but it's actually a lot simpler than I thought, so I will.

The method I use is to check for the existence of esb_typecheck . If it's defined, you're in ESB, if not, you're in DSB. (This is, admittedly, very similar to the method you described! But it's based on a function that is never going to change, so it should be reliable) if (esb_typecheck) then do_es...

I actually couldn't reproduce this, but my best guess at why it happened was that grouped monsters had a queued attack and they turned in between. For example, if a group of vexirks want to attack, the first one will attack on tick 0, and the second one will attack on tick 3. If the monster group de...

It would be fairly easy to let you just write text to the loading screen, but the loading screen's renderer is very simple. It retains the framebuffer between ticks and just writes things to the screen as it does them. This means (among other things) scrolling is impossible.

Adding this "feature" was actually in one of my April Fools posts a few years back. I certainly didn't intend to actually do it.

Both of those statements are (unfortunately) correct!