DBUser32478
Member
- Joined
- Apr 11, 2014
- Messages
- 193
- Reaction score
- 2
has done it multiple times now
this is latest log
xzjv told me it was to be posted here fyi
*I always grab the latest DB ZIP file open it in my DB Folder directly off C: and run it. It almost always has something outdated and lately it has been Adventure Plugin is what is outdated.
So I grab the new adventure plugin drop it in the plugins folder and upzip there. the problem is it creates a Plugin folder inside the plugin folder, so then I have to move it to the original plugin and delete then new unwanted plugins folder.
yesterday is the first time I just deleted the adventure file first and then unzipped it so it didn't have to overwrite files. arg as I explained it I realized even though I deleted the Adventure folder and then unzipped the new one I still left it in the secondary 'new' plugins folder....
why do you create the adventure plug in inside a plug in folder and zip it that way instead of letting the adventure plug in stand on its own? It would prevent this error.
I have run it now pulling adventure from the new plugin folder and putting it the original plug in next to trinity and it seems to be running fine
thanks for all your hard work DB is better off than it ever was before.
View attachment 267560 2015-10-06 18.45.txt
this is latest log
xzjv told me it was to be posted here fyi
*I always grab the latest DB ZIP file open it in my DB Folder directly off C: and run it. It almost always has something outdated and lately it has been Adventure Plugin is what is outdated.
So I grab the new adventure plugin drop it in the plugins folder and upzip there. the problem is it creates a Plugin folder inside the plugin folder, so then I have to move it to the original plugin and delete then new unwanted plugins folder.
yesterday is the first time I just deleted the adventure file first and then unzipped it so it didn't have to overwrite files. arg as I explained it I realized even though I deleted the Adventure folder and then unzipped the new one I still left it in the secondary 'new' plugins folder....
why do you create the adventure plug in inside a plug in folder and zip it that way instead of letting the adventure plug in stand on its own? It would prevent this error.
I have run it now pulling adventure from the new plugin folder and putting it the original plug in next to trinity and it seems to be running fine
thanks for all your hard work DB is better off than it ever was before.
View attachment 267560 2015-10-06 18.45.txt
Last edited:
