Home Creators Posts Import Register Favorites Logout

Content

After a brief break, some job interviews and other random life stuff - another update!

I realized I have no idea when the OBR update will come through that will make storage easier. So I designed a band-aid instead to hold everyone over until that happens.

Hopefully it won't completely jack up my database storage.

As you can see in the image - there's a line around the map. It's been stitched! Which is good news because this cuts down a lot of the lag of actually using the thing.

So what happens now is;

The map is generated based on the settings.

The files are grabbed from the server.

The images are stitched together and sent back for storage. (Could I have done this on the server? Maybe. But it would've upped my computing costs quite a bit, and I really want part of this to be available for free.)

Every user can store ONE map - but it's not really a big deal. The URL from my storage is used for the initial map image in OBR (Since I can't access the URL after uploading it in OBR..) - and at the same time, in OBR you'll see a pop-up asking where do you want to store the image. So if/when that one image on my server rolls over to a NEW image you made - you can just use Replace-Image in OBR with the saved map... sounds weird? A little. It only matters if you're generating a lot of maps, but the point is you won't lose the image. When OBR has the capability to give me back the URLs after uploading the map to your assets, I'll amend this step and it'll be smoother.

The map decorations are then added. Presto! All done.

This brings us to the post-generation stuff. I've added in two controls - Add Walls and Add Encounters.

With Generate Walls... You've already seen what it does, but as I mentioned before - this was always going to be a premium benefit. You still need to click it after generating the map though, because it doesn't hold the map in memory. (There may be some changes to that later, like saving the seed ID so walls can be generated at any time.. but I don't see this as a big deal. Who is making a map and then coming back later to decide to add walls. JUST MAKE A NEW MAP.)

With Add Encounters... I've decided I'm going to stick with CR for the first run. You'll specify a number, and it'll ping the database to grab monsters until it fills up that number. So saying CR10 might get a room with a CR5, CR3 and a CR2. Or maybe just one CR10. Who knows? Will it kill your party? Who knows? Maybe they should learn to run.The other thing is I poked Josh, as I wanted to leverage his database also. Not everyone uses Clash! and I want to make sure they have the freedom to add encounters as they please.

The only downside with Add Encounters is the tokens are going to be generic. (Like, maybe 3 different types.) Just because I'm not going to store a token for every single monster, or setup a key-match database to make sure the right one gets selected for each.

After that.. I think it's done? I've spent a good amount of time on the image processing today, making sure the file sizes stay down. The only thing not working currently is.. the Encounter Generator and I haven't fully tested out all types of map generation. I'm probably going to lock it to 'Basic' only to start, to save my sanity. But we're close. Probably this week? We'll see how the encounter stuff goes.

Files

Comments

No comments found for this post.