Pain. I had only made a small rebalance change of quality in our material array in material.c.

But this broke my treasurelist. So normally this means, if you chance the start quality of a material block, or add more materials or change the max ranges in material.c, you need to go in treasurelist and artifacts and must change ALL material_quality and ALL material_range definitions there. 

This is not a developer friendly logic. So i spend the last 4 or 5 days reading and trying to understand treasurelist and treasure.c. I commented code, made a lot of test runs, reordered the logic and improved the logic with two new features.

We can now define range 64 (or higher, it only checks for range>=NROFMATERIALS_REAL) and logic will autoadjust this to highest possible range for this material. Also there is no more need to define material_quality to allow the material_range command.

So a simply
material_range 64
without a definition for material_quality, works now and it don't cares anymore, if i adjust qualities or add more materials in material.c.

I must test this more and also check, if this works with artifacts too.

https://github.com/Kamor/Dolfo/blob/main/server/src/server/treasure.c