duckman

I can also confirm this. Looking at the commit the stuff I do understand looks right. So then I look at line 768 in ItemHandler.cpp and wonder if count_pos could mess it up. I don't have time to recompile my stuff right now, but maybe it requires a -1? Or is it line 735. Original had the item count, now it has 0. But I don't really see how that could shift stuff by one. I don't know... just throwing ideas out there :-P

The flag guy in ZM won't give me the flag. The gossip text appears fine but when you click it nothing happens. I am not sure how to debug this.

Sorry to say but I have encountered a problem. The reason I made this change in the first place is because I forced my DK through the DK starting area and discovered that he was short some talent points. I looked through the code and this seemed like the perfect fix. But now when he logs in his talents get reset. Looking through the code, I can't figure out why? It uses the same function I changed to figure out if he has used more talent points then he has supposed to. I will admit the change was made after he did the quests but I don't think that should have made a difference. I may have to try to make another one.

What bug does the patch fix? What features does the patch add?

When guests are used to define how many talent points a character gets, the rate should be considered.

For which repository revision was the patch created?

8075Is there a thread in the bug report section or at lighthouse? If yes, please add a link to the thread.

No

Who has been writing this patch? Please include either forum user names or email addresses.

Me

I didn't make a patch file because its a single line.

line 19460:
    uint32 talentPointsForLevel =
        (getLevel() < 56 ? 0 : uint32((getLevel()-55)*sWorld.getRate(RATE_TALENT)))
-         + m_questRewardTalentCount;
+        + m_questRewardTalentCount*sWorld.getRate(RATE_TALENT);

Pretty self explanatory. The talent points to be calculated after level 55 gets multiplied the way its supposed to but then the talent points from the quests is left alone. This fixes that. Haven't done a huge amount of testing but I don't see why this would mess anything up.

Mangadmin has some dev branches that work with 3.0.9. Not perfect but it does work.

I believe you can edit the db directly. There is a column in the accounts table in realmdb.

I'll wash your car!

wouldn't a better solution be to simply change the account on the character to like 0 when they get deleted. Then recovery is simply set it back to the account. And cleanup is to just remove anything with account 0.

dythzer is working on making a bunch of commands and one allows you to do what you want I think. http://github.com/dythzer/mangos/commit/1018666268e9826a1a74204b233e8f77c9092fe2

I agree with Dythzer. Will there be idiots who try to use the branch for real? Yes. Will they be annoying? Yes. But do we have to be nice to them? No. No where does it say Mangos is supposed to be used as an actual server. It is a platform for people to learn how something like a mmorpg is developed. Any real developer understands this and understands what unsupported and unstable mean.

I personaly am really interested in what it takes to go from one version to another. And if I have the skills to help I would like to. But if everything is done behind closed door I am learning nothing and can't even know if I could help.

Now this is sounding kind of like a complaint... Sorry about that. Not what I am trying to do. Ill shutup now...

There is an option in the config actually.

#    vmap.ignoreMapIds
#        Map id that will be ignored by VMaps
#        List of ids with delimiter ','
#        If more then one id is defined and spaces are included, the string has to be enclosed by "
#        Example: "369,0,1,530"

didn't post fast enough apparently :-P

Doesnt have to be exact time. Like something made for yesterday's commits would be 10162008_mangos.sql.

What if instead of using revision numbers they use the date of the git commit. (hehe that sounds soooo cool)