Gestrafe / maptracker

Automatically exported from code.google.com/p/maptracker
0 stars 0 forks source link

Spawn tracker - creatures not being tracked on rocks #4

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
When using spawn tracker there should be a function to check if it should
track monster twice i mean if the tile has been tracker before the monster
on the tile shouldn't be created.
Because in other way there will be such problems:
http://img683.yfrog.com/img683/9981/uo0007.jpg

Original issue reported on code.google.com by tibia147...@gmail.com on 3 Jan 2010 at 3:15

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Forgot to add it happens with 2x .cam files not with single one.
For example on first we are exploring a place with monsters and on second one 
same
place and monsters will be created 2x.

Original comment by tibia147...@gmail.com on 3 Jan 2010 at 4:24

GoogleCodeExporter commented 9 years ago
Also monsters aren't creating in some moveable ground like "rock" 
http://img34.imageshack.us/img34/4395/uo0008e.jpg
in this place should be monsters like ghouls skeletons.

Original comment by tibia147...@gmail.com on 3 Jan 2010 at 2:39

GoogleCodeExporter commented 9 years ago
@up
I think something else is causing that issue, because ZTracker also refused to 
place
npcs/monsters in certain areas of the map.

Original comment by cykotitan on 3 Jan 2010 at 10:50

GoogleCodeExporter commented 9 years ago
The first problem cannot be solved easily, because it looks like the problem 
you are
having is when monsters are near each other, but not on the same tile 
(MapTracker
already checks if there is a monster on that tile). I could make it an option,
however, where monsters have to be N squares apart.

For the second problem, please provide a link to a CAM file.

Original comment by ian320 on 4 Jan 2010 at 4:21

GoogleCodeExporter commented 9 years ago
There should be a option to check "if the tile is tracked before don't track 
monster".
It also happens with 1x cam when some1 has been in place 10 x time and saw 
single
monster.
Movie:http://www.speedyshare.com/files/20141588/farminecity.cam

Original comment by tibia147...@gmail.com on 4 Jan 2010 at 5:27

GoogleCodeExporter commented 9 years ago
Agreed

Original comment by huberto...@gmail.com on 4 Jan 2010 at 5:54

GoogleCodeExporter commented 9 years ago
Ahh I understand you problem. If it was empty before, don't retrack it. This is
actually a different change I made, so if you change the options and go back to
retrack, it will.

Original comment by ian320 on 4 Jan 2010 at 8:32

GoogleCodeExporter commented 9 years ago
If I recall right, ZTracker used to either assign unique ids to creatures once
tracked, to prevent them from being tracked again, or used creature IDs from 
client.

Original comment by cykotitan on 5 Jan 2010 at 1:00

GoogleCodeExporter commented 9 years ago
well z tracker had same issue with "if the tile is tracked before don't track 
monster"

Original comment by tibia147...@gmail.com on 5 Jan 2010 at 1:34

GoogleCodeExporter commented 9 years ago
I've fixed the retracking problems in r28.

Original comment by ian320 on 5 Jan 2010 at 8:49