Hackers triumph over pricing.log beast-file ...

[Magnate]

For those on the bleeding edge, r1373 now truncates the pricing.log file every time you (re)start the program, which means it can't get out of control unless you play for months at a time ... it also means that if you spot a pricing anomaly, you need to post the relevant bit of log file before the next time you start the game.

Thanks to Paul Blay for the code ideas - I had a look around play_game() and init_angband(), but there wasn't an obviously better way to do it.

Now, if I can just work out why it calls object_value twice for every object, I can halve the size of pricing.log still further ...

[s0be]

You could just try to mark the file read-only. (I haven't tried it)

[Magnate]

You could just try to mark the file read-only. (I haven't tried it)

?? Why would one want to do that?

[s0be]

For those uninterested in viewing the log or reporting back the results of it, that might prevent it from growing. It might just prevent the program from running too.