Putblock Data Table

[dabyx]

Hello everyone,

Just wanted to clarify.

PUTBLOCK adds entries to a data table in adventure mode which will eventually fill up memory but if not using adventure mode PUTBLOCK can be used many times and won't add to the memory usage in a completed game correct?

I have been wary of using it. 😅

Thanks very much.

[mas]

Morning! My understanding is tha you're correct (someone with more knowledge of the engine will probably reply with the technical hows and whys).

From what I see in my use of PUTBLOCK in non-adventure mode. The blocks do not persist. As soon as you redraw the screen, or leave and come back, the Blocks are back to the way it was. In adventure mode, it (should) be recording the differences on screen where putblock has been used (e.g. you open a door, door should be open when you go back or the screen redraws etc).

I've used PUTBLOCK heavily in my last 2 games (MoneyMouse uses it for the 4 mini games, ShovelDuck II uses it for diggable blocks, open/closed doors/spike traps/vertical scrolling/openning and closing areas of the game).

I assume that MPAGD/AGD has a 32x24 "blockmap" for the current screen. Any putblock things update the display with the block and this blockmap with the type of block.

In adventuremode it would update the current screen / blockmap and additionally record that screen Z has a block at X Y changed to block number W ... ...but I've not messed with adventuremode so will leave it to someone else to explain why I'm wrong :-)

(Is my understanding of regular PUTBLOCK right? I think if it wasn't my games would crash very quickly as they're usually approaching the memory limit without worrying about a blocktable growing at the end of memory)
M.

[dabyx]

Briliant, thanks!

I thought so but was just a bit worried that it would still use memory. 😁
Unfortunately not had a chance to play your games yet (or any at all! Too busy!) But love the look of them in videos 😄 and they are in the queue! 👍

[mas]

No problem. Yeah, the manual covers a lot of stuff but only mentions the putblock list with the adventure mode settings briefly. I'd be wondering what happens if I change the same block multiple times? Would it store each, or optimize to "the last current putblock at that position etc." ?

For the mostpart, I'm happy with having a condition (like having got an object, or setting a variable to track things etc.) over tracking putblock changes.

It's definitely been a good year (so far) for games; I've put a bunch on my "will pick up after I finish coding this next game" list. I'm trying to avoid playing things in a similar genre to what I've been working on so I don't get overly influenced by someone else's game mechanics; some people have great ideas / implementations of things I've not seen before, and it does sometimes have you going, "why doesn't everyone do this?" ( an example being the hiding / ducking idea in Mushroom Soup; it's interesting, different, and does feel like a "why isn't everyone doing this?" mechanic :-) )

Thank you for the compliment on my games. I feel each one is a learning exercise and I come out with "a bit more knowledge of what I'm doing" over the previous one. I'm currently working on a few "bonus" mini-games to be made available alongside Shovel Duck II, but part of what I'm doing here is trialing things and getting some routines together I'm planning to use for my next game. I tend to have a good idea of what I'm aiming for in my head, and what I need to do and get working before I start coding properly...

Looking forward to seeing what you're working on next.
M.

[dabyx]

Yea, it's always a thought of trying not to be too influenced! Although there are plenty of games that make it their own. I see a lot of newer games be praised for ideas that are exactly like old 8bit games 😁 I'm surprised how much people liked Mushroom Soup honestly 😅

Sounds like you are very organised and prepared!! And seem to know a lot more technical stuff than I! 🙂