Thanks!

Here's one way to do the falling rocks:

https://dl.dropboxusercontent.com/u/542 ... rdash.capx

It differs from Bertie Booster's idea in that it uses a array for a grid instead of using overlapping at offset.

your capx is really great R0J0hound and i just finished adapting it to use with a tilemap but it seems my way of looping though the tilemap to find the "rock" tiles is far more cpu intensive then your "for each sprite" loop.

is there maybe a better way to find the rocks / loop through a tilemap?

i also tryed the following, but it doesnt make much difference, i think.

as soon i have something worthy to show i will show it here!

just realized that in the screenshot above theres some mixup, event 13 has the wrong parameters, instead of "character.nodeindex+1" there should be "loopindex" so it checks the whole remaing way for obstacles. With the parameter "character.nodeindex+1" it only checks the second next tile the character wants to move to.

I made this because i ran into another gamelogic problem, the "all seeing eye characters"

They shouldnt know where on the whole path people are standing but they do when i loop through the whole remaining path, the same problem appears when they calculate paths anyway, so i think i have to find another solution where i dont set the tiles characters standing on to non-walkable.

After some sleep i thought of using two tilemaps (im using at least two tilemaps anyway for ground, interior, etc..). First tilemap for ground and outer walls of buildings to provide the characters basic knowledge of theyre neighborhood and used for the initial path calculation. On the second tilemap i save the positions of characters and inner walls. While the character moves from tile to tile it could check if theres something in theyre field of view and whether its necessary to change the path. The characters then will need some form of memory for things they saw, a string where it remembers additional obstacles, that will be added before calculation and removed afterwards, so other characters can use the basic map with theyre own knowledge of temporary obstacles.

Im curious if this makes sense and works like i think

New roguelike/RPG expansion available!

Download: http://www.kenney.nl/assets/roguelike-modern-city

wow, this is really nice! Thank you!

i changed it to this and it works, maybe someone can use it too

Thanks again!

so im tinkering around with this plugin some days now, its really awesome and easy to use and the performance is so great that i came away with some ugly logic but now is the time where i came to a deadend with my ugly logic

my idea was to ad the positions of characters on the tilemap as additional obstacles, remove them when they change theyre position and add the new position as an obstacle. I couldnt find a way to check for this event efectively so i chose the every tick method seen in the picture. It works, but when i came to the point that characters should also check if there are new obstacles when they move along theyre found path, the only working "logic" i could find was the "every 1 second->recalculate path" which is, together with the every tick for every character remove and set obstacle, really, really bad and i think the performance will also go down when its used in a real game.

i bet i have to tie it to the moving part but i cant find anything that works.

Do you have an idea?

wow, you are absolutely amazing! im very, very thankfull and happy

fldr Yeah, I deliberately set empty tiles as walkable since I believed that'd be the most commonly wanted behavior... However, you can easily have an a non-empty tile with all transparent pixels and set it as non-walkable.

after i worked some more with it, i fear a bit to ask... but could you maybe please make an option to set empty tiles walkable/not walkable?

Thanks! i kinda already did it that way as a workaraound

it seems that when no tile is placed the plugin takes that as walkable, can you give any tip how to avoid this?

thanks for this nice plugin!

i did often read about slow preview times with many sprites but thought it cant be so worse..

now i got to a point where its just ridiculous, in a project with 600 24*24 Sprites (one sprite object, so would be one spritesheet) and 200 16*16 (another spritesheet, so we would have two now), a total size of 50kB, its faster to export the game, find a failure, fix the the failure, export again and run the game compared to just previewing it, the preview is at that time at ~50% loading.