[DiscordArchive] Hi! Is it possible to have DBCs in DB being loa...
[DiscordArchive] Hi! Is it possible to have DBCs in DB being loa...
Archived author: stoneharry • Posted: 2024-11-25T15:11:44.622000+00:00
Original source
It's simple really.
Extract dbcs from client, the same you would for running a server.
Import those into spell editor, import into mysql once.
Forever more you can edit your dbcs in MySQL and just use the headless exporter to turn back into dbcs when needed
Archived author: Vel • Posted: 2024-11-25T15:12:44.825000+00:00
Original source
Yes, but sadly not possible for me rn.
Archived author: Vel • Posted: 2024-11-25T15:13:14.541000+00:00
Original source
I have only modified DBCs at my hand now. But that loops the app.
Archived author: stoneharry • Posted: 2024-11-25T15:14:01.873000+00:00
Original source
It seems like you made bad edits. That's on you to resolve. Spell editor will make some assumptions on how to fix the data, I.e: it will just drop duplicates after a key with that Id has already been read.
Archived author: stoneharry • Posted: 2024-11-25T15:14:42.205000+00:00
Original source
Spell editor can only work with good data. If you provide it bad data, it doesn't know how to handle it
Archived author: Vel • Posted: 2024-11-25T15:14:45.559000+00:00
Original source
Yeah, that's what I want to test. Whether the loop is because my Windows and Spell Editor are not friends or because our DBCs are corrupted.
Archived author: Vel • Posted: 2024-11-25T15:29:42.192000+00:00
Original source
Nah, it's the same result. It seems after all DBCs are imported to the server it starts to throw:
```
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
```
And loops unlimitedly.
Archived author: Vel • Posted: 2024-11-25T15:29:47.861000+00:00
Original source
I imported fresh DBCs.
Archived author: Vel • Posted: 2024-11-25T15:30:50.587000+00:00
Original source
message.txt
Archived author: Vel • Posted: 2024-11-25T15:31:50.989000+00:00
Original source
This goes wrrrm in a loop and spams it (debug log growing above 100 MB just under a minute)