the tables in which ID matters (all linear scale):
- items - loottable - lootdrop - npc_faction - doors everything else shouldent matter. |
Quote:
|
Now that I've tweaked the increments to tighten up the id ranges, and we've not had too many bug reports, I'm looking for more features to add (or maybe a new project?). Any requests?
|
Excellent! :D
What about ground spawns? There are quite a few quests and items that do spawn on the floor. Oh, and items. I'm sure people with custom servers and items would like that option. I'm not one of them, but I could imagine the pain it would be to export/import everything every single time. Um, that's all I can think of, heh. |
Quote:
Nice work, still. Very helpful scripting. |
Zephyr, one more thing. MySQL 4.1 doesn't seem to be handling this header line very well:
Code:
print FILE "-----------------------------------------------------------------------\n"; I edited my .pl and re-ran the scripts and MySQL can import the file ok. Not sure if this is everyone, or just my version (MySQL - 4.1.20-community-nt). |
Quote:
|
Quote:
I've patched the program and re-posted it. |
Excellent. Thank you again for this. This script kicks ass!
|
It's all in the numbers
Quote:
After you run zephyr325's tool, you'll have , new "groups" of high rows/numbers - with "MySql Query Browser", you can sort them so you can see all this; you can see where the original set of numbers end, and the new sets (you made with the tool) start and end. So, for example, lets say lootdrop originally has ids of 1 -10, and the tool made 10 more rows 20-30. so now you have rows 1-30, the gap being rows 10 -20 so you have to optimize and move the new ten rows to start at 11. Code:
UPDATE lootdrop SET id=id-9 WHERE (id>=20 AND id<=30); Here's some examples of what I touched when I fixed my database. Code:
UPDATE lootdrop SET id=id-14878 WHERE (id>=102100 AND id<=102200); Code:
UPDATE npc_types SET loottable_id=loottable_id-14878 WHERE (loottable_id>=102100 AND loottable_id<=102200); I haven't used zephyr325's tool yet , but I'm sure the same thing happens to him as what happened to me, when this tool is run. Also remember, just adding/merging Cavedudes' and PEQ is not the whole solution - it's just a "better start" to what needs to be done. |
I forgot to add the reason for the calculator ;
Code:
UPDATE lootdrop SET id=id-9 WHERE (id>=20 AND id<=30); Highest old number(10) subtract from lowest of new numbers(20) = 10, then subtract one from your new number(10 - 1) to get 9. You need a calculator for whan the numbers get big and ugly. |
0.5.7 database
FYI,
I tried to update a 0.57 and a 0.6.0 database and this pops up. Use of uninitialized value in concatenation (.) or string at grabnpc.pl line 740 not a clue on what that means but line 740 is this. print FILE "\"$Spawn2[$tmp]->{'Condition'}\","; guessing it has to do with spawn conditions and such. |
Quote:
A bigger question is whether or not the 0.6.0 version of the program needs that variable for something. I'm not sure about that one, but I'd just source one NPC to see how it acts. |
1npc
Quote:
last year I was able to convert it over to 0.6.0 but I added and deleted a whole slew of fields. The NPC sourced in but it's not showing up in the spawnlistand if i remember right I had to drop and add quite a bit of fields. so the conversion from 0.6.0 to 0.7.0 is what im troubleshooting atm. |
Parseing error.
this is right from the npc file that grabnpc.pl made.
After tinkering with it for a while I noticed this error, maybe it's a parseing error. mysql> INSERT INTO spawn2 (id, spawngroupID, zone, x, y, z, heading, respawntime , variance, pathgrid, timeleft, _condition, cond_value) VALUES ("350904","281356 ","nexus","0.977219","19.124527","-30.247982","139.125000","1200","0","0","0",); ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1 |
All times are GMT -4. The time now is 02:21 PM. |
Powered by vBulletin®, Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.