@*Astalion*
I've just discovered the **/you** tag, that's why you see your name.
i was in humorous humor when i write this post, and wanted to make a small surprise.
It's funny to be able to say:
/you is reading this post.
@Joel
I've read you update on beta CW-AT, i think with one or two character class and 50%+ of the monsters, we can start the beta test.
We will see maps issues, quest issues, monsters issue...
It is also better to start with few elements to determine where each bug come from.
If there's a bug cause by a particular skill, on a particular monster, you'll don't know if the bug come from the skill or the monster.
If you have started with this monster and the skill unavailable on the beta, then you'll validate the monster.
In public beta, the problem emerge, you'll then test the skill and easily conclude this specific skill/monster problem.
If the two are active on the start, this conclusion won't be that easy.
You'll have report:
Monster X cause crash.
and other
Skill Y cause crash.
Hope this help to prepare the debbuging process.
EDIT:
DONC a part pour les gossips, j'enverrais les fichiers txt du mod avec qqs annotations
et sans les données
Ouf, le plaisir de la decouverte restera intact.
