⚂ Thanks,
Not much of informative demonstration, but is cross-platform and shows performance.
Common solution to this problem is to create a 'cache' image that would hold a tiled version of image to be drawn easily.
That means drawing image W*H times only once in a while.
However, actually you can do even better than this.
Continue reading
Possible future candidate for an adventure map
From my point of view, creating a tool, that would perform your desired action efficiently, is often better than just doing mentioned thing.
In last few days I've developed a small tool that translates given commands into series of WorldEdit plugin commands, and provides simple interface for writing dynamic scripts that modify world contents, even without having access to server to be able to import JS scripts.
Since game handles input nicely, a single message can be sent every 200..300ms, meaning that subset of commands needed to change selection bounds and perform desired operation over it often takes less than a second to perform, in comparison to minute-measured time needed to do same manually.
This opens rather interesting perspectives of automating creation of typical structures, as well as making it possible to push procedurally generated content into game easily.
Yesterday I've spent some time to port part of RPG05's dungeon generator for use with this, and this is the result.
Looks nice enough, right?
In free time of last days I've been developing earlier mentioned thing in Love2d, which is platformer engine.
One provides a simple framework for games that use combination of aligned tiles and dynamic objects.
As well it adds a easily modifiable system to load levels from strings, giving freedom for implementing level editors.
You can download a compiled version here or watch discussion thread on official forum here.
Love2d only provides you with a function to check if specific key is currently down, love.keyboard.isDown(key), and no functions to check if key was pressed\released.
But there are events, which can be used to implement such functions.
Code below demonstrates sample implementation.
If you've been working with Love2d, you might have noticed that there isn't an actual debug console, and print() calls will not get displayed anywhere.
However, it's pretty easy to make your own system to display single-line output messages.
Here is an example of one.
Can be seen as a part of those block-building games
So, today comes with an example of collision between point, box, and line versus a 3d array.
3d array is presented as ds_list (z) with ds_grid's (xy).
Functions include management of this 3d array (creation, destruction, modification - no memory leaks included) and actual functions to check for different collisions.
All of these also include error handling, so attempting to check for collision outside the 'map' will threat area as 'air' (0) and not crash the game.
Also note that no optimization was applied to process of block rendering - you'd likely have to change that if basing game with large level on this example.
As you might have noticed, process of making nice-looking isometric games can be tricky.
Especially that part when you want your terrain look like actual terrain rather than arrangement of isometric images.
Common approach to this is to use alpha channel mask(s) to smooth edges of tiles.
Here I've made a script that applies such mask to given sprite, handling all additional actions needed.
While working with GameMaker, you might have noticed that all collision_ functions return only first instance to intersect given collision shape, while in some cases you'd want to get all instances that collide with one.
This set of simple scripts adds such missing functionality...
You might have met such situations where you need to find nearest coordinate at object's edge towards a point, or find actual (non-bounding box) distance between objects, or other things of this kind. If so, you may find this example useful.
Used method is relatively simple - first find approximate distance with distance_to_point function, and then 'fix precision' by using a 'while not position_meeting' loop.
This way maximum amount of calculations will be limited to cP * iR + dP, where
cP is time needed to check object for collision against a single point
iR is instance 'radius' (maximum distance from origin to corner of bounding box)
dP is time needed to find distance between object's bounding box and point
So it should be acceptable for many cases of usage. If you need to reduce amount of calculations further, could alter distance decrementation 'rate' in two while loops. Removing while() loops entirely would give rather approximate distance calculation.
Today I've made a example of implementing local highscores (via webdata functions) and user input (via keyboard_check_*... at least until I'll add some code to event handles in framework) in Tululoo.
![[dinosaur peeking in from the right] Hey! I now have a newsletter! Come take a look.](https://yal.cc/wp-content/themes/dotpage/images/mailing-list.png)