GENERAL

What error you get? There is no landmark limit in the code.

official clients I tested for linux and windows does not have landmark limits like you describe.

1.   I am not suggesting such a thing is encoded in the current releases as it was before (I had seen it an an old post of yours, which is where i got the 256 from).

All I can say for a fact is that I was iunable to create one ... 9 times and at different locations and that deleting two, let me create another 2 but not a 3rd.   Perhaps the official Win64 client is different from the single folder install on soundforge ?  Perhaps it was a fluke associated with something outside of Ryzom or a one time thing.  Perhaps I created and then edited / moved to many flags and kami gods were punishing me

I have had at least a dozen missions in the last week fail to complete, I don't know why either, but in all but one case (12 Kirostas died, no creds), as with the markers,  relogging made them work.

2.  Regardless, if it happens again, thanks to your input, I know what not to consider.   I should tell ya that I kinda remebered the limit being removed, at the time wondering who could ever fill up the limit.   But hey at my age, you have to wonder, so thanks for letting me know I don't have Alzheimers :)

If it ever does happen again, it would seem I can eliminate it by relogging ... if someone else experiences it, at least there's a workaround that can be tried like using "follow" instead of the macro to make meks appear.

3.  Since there is a simple work around, I don't want to waste any more of your time on it, however I was hoping to get  your thoughts on  c) and d)  from original post.

c) We have any shot at being able to filter an entire category ? Liken Citizens only or Citizens and Mission mats only ?

d) Can we provide / export anything to add Missing NPCs to BM Maps. Was going to try Lopy's app but I dunno if that  or any other form of data collection would be  useful ... and peteJ not around to ask

There is no easy way to make gui for it. There is /mapsearch command if one wants to make shortcuts (there is no command to clear search tho)
NPC's are easy to find. Look for radar, it shows if any is in range, if they have mission for you, or if you have something to give them.

I have categorized all the mission givers as "Citizens". It just seems odd that it is very easy to filter a specific NPC (i.e. Bar'Nappy Nar'Kolepsi) and show the 4 locations that he / she rotates between


I wrote an extensive post on this very subject a few weeks ago ... To my mind it's supposed to be hard to find them ... the 1st time. However, the way fame is structured, it's exhausting to get those last few levels (took 12 hours to go from 96 to 100 doing nothing else. So, if we could filter my map for all "traveling NPCs in a region" we could minimize the back and forth and plan a route. Discovering where something is is fun ...but rediscovering every time I have to repeat something is frustrating.

But thanks for the info, seemed like it would be a simple thing, but looks like I misjudged. Perhaps I could rename them with the Tribe Name and name so I can use the existing filter function (w/ say Ecowarriors) to accomplish this goal.

As for mapping all the locations for others to access, we are working on a mapping app at present. In the meantime, we can add them to silenda maps as needed.

Thanks again for the feedback

Two hours for an OP is too long.

It is in testing but we lacking testers.

@Fyrosfreddy

Bug tracking and fixing is not working well.
- When a bug from a ticked gets to the board, it usually lack details because it links to the ticket. However tickets can be read only with permissions.
- Many issues not coming from tickets are not registered at all, it is very common that the issue is solved or forgotten and no one else knows about it but one team member.
- When you already have a well documented and confirmed issue, you still need someone to fix it. If it is not critical, it is usually left for the unspecified future.
- When it is fixed, it is hard to find any testers. And if, the deadline for testing is right before release so last not critical issues remain not fixed in many cases.
- And the worst, we hide many issues in a "Minor issues box" and no one willing to work on it unless it is critical. We are hurry to bring new changes, but we have usually no will to do the last step and finish it.

I know about 156 tasks related to various issues, we have 22 issues in progress and other 37 tasks as confirmed.

I WISH WE DEDICATE ONE RELEASE CYCLE JUST FOR FIXING.
Well, in fact, I wish we dedicated every other release just for fixing.


I try to track as many issues as possible, you can let me know.

i think it would be nice if plushies were flagged as exchangeable. The yubo used to be able to be given to a friend, now none of them can be.