[DiscordArchive] yes i did i have had no problems in the past with other servers making new spells but with this serv
[DiscordArchive] yes i did i have had no problems in the past with other servers making new spells but with this serv
Archived author: lungs • Posted: 2024-03-07T23:03:41.902000+00:00
Original source
yes i did i have had no problems in the past with other servers making new spells but with this server it has the dbc sql tables which is a little confusing does it also need to be put in there also or as normal just put in the dbc folder and mpq with the normal sql made for it to work?
Archived author: Young Toto • Posted: 2024-03-07T23:19:02.829000+00:00
Original source
If you mean the dbc tables in the world_db, those override certain things from the actual dbcs. If youre adding a new spell then you shouldnt need to touch that table (not 100% sure on this, but ive never had to touch it for adding new spells)
Archived author: Young Toto • Posted: 2024-03-07T23:21:47.854000+00:00
Original source
I ran into an issue where the first spell I tried adding wouldnt work but subsequent spells I added did work. Might be worth trying to make a new spell that does nothing before adding the new spell you actually want to add, as that worked for me
Archived author: Rymercyble • Posted: 2024-03-07T23:25:01.458000+00:00
Original source
u could add it through _dbc but since it needs client patch there is no reason to do that when u already need it in dbc
Archived author: Revision • Posted: 2024-03-07T23:28:21.004000+00:00
Original source
The idea behind the _dbc tables is that it loads the data from the DBCs and then from the corresponding table and uses the data from the table to override data loaded from the DBCs - however that doesn't automatically mean it can't be used to add new spells, although as Rymercyble pointed out (and I do agree) what's the point in doing it that way if it needs a client patch anyway.
I wasn't being clear. Loading from the tables could be it loads specific ids but that wouldn't make much sense. It makes more sense that it loads it into the storage after the file and just overrides when an entry already exists.
Archived author: lungs • Posted: 2024-03-07T23:30:27.511000+00:00
Original source
i got over 250 new spells already made up in the spell dbc file and have it and in a mpq which did'nt work so i tried exporting the spelldbc to sql file and putting it in the world db and that didnt work. So im going to to rewrite the spell dbc and leave it out of the world db after i recompile and take out a couple of mods
Archived author: Revision • Posted: 2024-03-07T23:31:27.104000+00:00
Original source
If you're using a client patch, using the _dbc tables is pointless. Just place the .dbc in the same folder as the original on the server side and be done with that side.
Archived author: Rymercyble • Posted: 2024-03-07T23:31:38.207000+00:00
Original source
When u make new spell u just need to add that dbc to server and to client and it will work
Archived author: Revision • Posted: 2024-03-07T23:32:13.038000+00:00
Original source
I understand that's what you did, but I felt it was important to point out that porting it from .dbc to sql is another step not giving you any advantage at all.
Archived author: Rymercyble • Posted: 2024-03-07T23:34:30.955000+00:00
Original source
Actually it would make more sense to do it in reverse have it in SQL for better management and export it to dbc just bcs client needs it