06-06-2012, 01:51 AM
LateTick isn't needed right now, I thought that I could use this that way:
One plugin calculates some information about player, writes it into .ini. It all happens in Tick()
Another plugin reads that .ini on LateTick(), so it's sure that first plugin had done all it's logic. But then I had that thought about cIniFile class
And still had no time to check it...
As for generation:
Two example situations. In first you write your own ore distribution, and completely replaces generator work. In another you simply add some ore type (or structures!), and want to add it AFTER generator (or another plugin!) did all it's job.
I can see no way one hook can handle both situations. I mean, in one case you have to abort generator's work, in another you want to add some changes after it's done. And you can even want to add something BEFORE generator start!
One plugin calculates some information about player, writes it into .ini. It all happens in Tick()
Another plugin reads that .ini on LateTick(), so it's sure that first plugin had done all it's logic. But then I had that thought about cIniFile class
And still had no time to check it...As for generation:
Two example situations. In first you write your own ore distribution, and completely replaces generator work. In another you simply add some ore type (or structures!), and want to add it AFTER generator (or another plugin!) did all it's job.
I can see no way one hook can handle both situations. I mean, in one case you have to abort generator's work, in another you want to add some changes after it's done. And you can even want to add something BEFORE generator start!