2009-10-31, 05:46 AM
Well I think many of the parameter editor tabs all output the same basic type of pr2 and prm files. So this is useful info for some, and probably not for others. It's a shame a proper truth glass on monsters was never implemented. And it's kinda dumb the monster description box was left inside the editor even though it's never used. I could technically fetch that data for a game, but it would be just as easy to fetch it from a file someone made, so the fact that it's in the output data is not a huge deal.
If you put an on death event on every monster to raise a flag to add that monster to a killed list or whatever you could gradually make the monsters available in the menu system. I'd probably do something more simple like add an in game manual, and open up more pages as the player progresses from map to map. Another way to go is to let some instance of the monster drop an item that unlocks the info. If you were going to put a kill event on every monster you might as well just make it a truth glass event. But you could have it print out something simple, then substitute the description later (via translation) so you wouldn't have to go back and edit every single description message, and maybe so the message wouldn't take up so much space in the evt files over an over (but I guess that would eat up your events... now I'm just rambling)
If you put an on death event on every monster to raise a flag to add that monster to a killed list or whatever you could gradually make the monsters available in the menu system. I'd probably do something more simple like add an in game manual, and open up more pages as the player progresses from map to map. Another way to go is to let some instance of the monster drop an item that unlocks the info. If you were going to put a kill event on every monster you might as well just make it a truth glass event. But you could have it print out something simple, then substitute the description later (via translation) so you wouldn't have to go back and edit every single description message, and maybe so the message wouldn't take up so much space in the evt files over an over (but I guess that would eat up your events... now I'm just rambling)