karastra

ok thanks for your answer Vladimir I have tried to analyse the 11560 patch (implementation of .mailbox command) to understand how it's run, and I thought that if it was possible for the mailbox that was for guildbank. It seems I was wrong

Hello, Sorry if the subject exist but i didn't find anything about it ! I fthink this command would be very userfull for GM ! I see where to make modification in sourcecode but I'm very bad in c++ So for me the modification must be in : - table mangos_command -> ok - chat.cpp -> I think I know how to modify - chat.c -> idem - level3.cpp -> idem - worldsession.h -> i'm not sure - playerhandler.cpp -> not sure - guildhandler.cpp -> I am completely lost (I don't even know if it is the good file)

You can easyly block the usage of the extension in the realmd base. Table : Account. There is a Field Named Expansion. If the value is 0 player can use no extension, 1 TBC, 2 WOTLK. After i think there is little work to adjust the stats of different element like items, creatures, ... but by tables comparison it's not impossible.

Hello, i think you can't do that without client alteration. I think opposite will be easiest : Using a 3.3.5 client and configure account & DB to block extensions possibilities.

good job

Thank you Vladimir for your Answer

Ok thank you for your answer. I'll try to modify this. It would be a good challenge for me, because don't know the c++ well (but i can make some basics changes).

Hello, I have another problem. Since several version, when i type .goname player in game, my character seems to fall in empty and die. I must retype .goname player in ghost mode and after .revive Mangos version : 11580 (no patch) [the problem have began earlier] SD2 : 2153 [same] Database : UDB 401 - Acid 3.0.8 (No Custom Content). Compilation : VC 2010 Express on Win 7 32bits Is it a core problem ? Or is it my installation ?

Hello, Breakwater Thanks for your answer. I haven't been clear enough in my description sorry. I know the difference between warning and error and even it isn't dramatical, I thought that was usefull to report these warning to devolloper for them to maintain a good code, because I know they do an excellent job

Hello, Today I was 2 error when I compile the core : 3>..\\..\\src\\shared\\Database\\Database.cpp(54): warning C4018: '<=' : incompatibilité signed/unsigned 3>..\\..\\src\\shared\\Database\\DatabaseMysql.cpp(430): warning C4018: '<' : incompatibilité signed/unsigned The compilation end correctly but I would indicate the error. Mangos core : 11586 (no patch) Compiled on : VC 10 Express on Windows.