KevlarBR wrote:Silvazar wrote:I am in the exact same predicament. did you have any luck with it?
I didn't have the balls yet to run it, but I think I will. Trees are getting on my nerves, man... But I think it is, yes.TheZar wrote:It needs to be put at the end of Dump.sql
Dump.sql or Patch.sql? I'm not sure. Anyways, what I think I'll do is shut down the server, back it up, run a query with the code to remove the trees, add the tree spawn removal code and start the server again...
Silvazar wrote:KevlarBR wrote:Silvazar wrote:I am in the exact same predicament. did you have any luck with it?
I didn't have the balls yet to run it, but I think I will. Trees are getting on my nerves, man... But I think it is, yes.TheZar wrote:It needs to be put at the end of Dump.sql
Dump.sql or Patch.sql? I'm not sure. Anyways, what I think I'll do is shut down the server, back it up, run a query with the code to remove the trees, add the tree spawn removal code and start the server again...
I hate to let you be the one to try first KevlarBR but did it work out? I am spooked that it will end up corrupting my database and all the poeple on my server will lose all their work.
Woundedcern wrote:this mod works fine but the problem i was haveing was everyone keeps saying to mod wrong file, the file that needs to be moded is the dump.sql file. mod is a one time use mod so doesnt run while game is running only on restarts.
Wir3tap wrote:This not working since last patch now? This sends my server into boot loops now if added to dump.sql.
DELETE forest, forest_patch
FROM forest, forest_patch
WHERE forest.GeoDataID = forest_patch.GeoDataID
AND forest.Quality < 40;
SET @c442 = 1;
SET @c443 = 1;
SET @c444 = 1;
SET @c445 = 1;
SET @c446 = 1;
SET @c447 = 1;
SET @c448 = 1;
SET @c449 = 1;
SET @c450 = 1;
UPDATE forest_patch
SET Version = @c442 := @c442 + 1
WHERE TerID = 442;
UPDATE forest_patch
SET Version = @c443 := @c443 + 1
WHERE TerID = 443;
UPDATE forest_patch
SET Version = @c444 := @c444 + 1
WHERE TerID = 444;
UPDATE forest_patch
SET Version = @c445 := @c445 + 1
WHERE TerID = 445;
UPDATE forest_patch
SET Version = @c446 := @c446 + 1
WHERE TerID = 446;
UPDATE forest_patch
SET Version = @c447 := @c447 + 1
WHERE TerID = 447;
UPDATE forest_patch
SET Version = @c448 := @c448 + 1
WHERE TerID = 448;
UPDATE forest_patch
SET Version = @c449 := @c449 + 1
WHERE TerID = 449;
UPDATE forest_patch
SET Version = @c450 := @c450 + 1
WHERE TerID = 450;
SET @c442 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 442
ORDER BY TerID);
SET @c443 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 443
ORDER BY TerID);
SET @c444 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 444
ORDER BY TerID);
SET @c445 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 445
ORDER BY TerID);
SET @c446 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 446
ORDER BY TerID);
SET @c447 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 447
ORDER BY TerID);
SET @c448 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 448
ORDER BY TerID);
SET @c449 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 449
ORDER BY TerID);
SET @c450 = (SELECT
MAX(Version) AS max
FROM forest_patch
WHERE TerID = 450
ORDER BY TerID);
UPDATE terrain_blocks
SET ForestVersion = @c442
WHERE ID = 442;
UPDATE terrain_blocks
SET ForestVersion = @c443
WHERE ID = 443;
UPDATE terrain_blocks
SET ForestVersion = @c444
WHERE ID = 444;
UPDATE terrain_blocks
SET ForestVersion = @c445
WHERE ID = 445;
UPDATE terrain_blocks
SET ForestVersion = @c446
WHERE ID = 446;
UPDATE terrain_blocks
SET ForestVersion = @c447
WHERE ID = 447;
UPDATE terrain_blocks
SET ForestVersion = @c448
WHERE ID = 448;
UPDATE terrain_blocks
SET ForestVersion = @c449
WHERE ID = 449;
UPDATE terrain_blocks
SET ForestVersion = @c450
WHERE ID = 450;
Wir3tap wrote:I read earlier it was dump.sql has this been changed back to patch now?
Estharos wrote:Is it possible to role back that coding, we are experimenting problem with it, we put the code in the dump.sql file and though it will role back if I put back the original dump file back but it didn't not.
Cheers,
HahlgrimtheThane wrote:Hi, can any server admins confirm if this script still works with latest patch.
I have previously run this script using HeidiSQL and just run as a query on lif_1 database . But we ran into some problems with oaks, apples and some other trees disappearing.
So I was just wondering if the script still works.
Thanks.
I've done some simulations over the past couple of weeks to get a better understanding about the forest maintenance XML file to make an actual generator with UI for it.
Conclusion: This 'desert' issue can't be reproduced without the use of obsolete and possibly harmful forest cleanup sql scripts. You can hardly blame the devs for the ignorance of some server admins, honestly.
Values above 1000 for maxage/deathborder will result in fewer trees to be planted. Values above ~1500 will result in no trees being planted at all. Once all initial trees died, the server will be empty.
To be fair, I don't really see any reason why you would want to configure such sky high values for tree age. But since there is no upper limit mentioned in the XML comments, I would assume this is a bug indeed.