Try putting the campaign stuff in a hak as much as possible is my only real suggestion. Not sure if that is something that will work since some things just have to be in campaigns, but they don't seem to work as well with. Regardless one hak with that stuff is much better than a bunch of loose small files for over all performance.
Worldgate had it's share of issues as well, for the most part the issues with the ADL are all on the PW Admins side, where before the issues were with the end users. Since the PW admin is a lot more sophisticated relative to the end users, its a lot better now.
The big issue is just doing things step by step and not skipping things, and i've helped quite a few PWs get up and running. Generally the first time it works fine, but eventually they get more lax and start trying to speed things up and it gets hairy. However campaign files seem to have other issues.
The way i help folks solve problems, ( i was one of the first PW's to get up using the ADL and have helped a lot of PW admins sort out the issues )
1. Looking at the actual log files for the end users and the server, which is really the first step. ( in your temp folder %temp%\\nwn2 ) Can't remember the actual log paths but there is one for the server program, and one for your client, and you need to make sure you are on your actual server when you look at the server one, and vice versa.
2. If a file is an issue, go ahead and delete the lzma it creates, to force it to recreate the lzma and put that checksum into the lzma. Might be multiple files, so deleting all recently changed lzma, or files you know should have changed is advisable. In extreme cases deleting all the lzma is useful.
If you deleted a file entirely, well the toolset won't delete it from the xml file, so you will need to edit the xml file to remove it, or just delete the xml files entirely.
If the file is not even downloading at all, check that your ftp site or drop box has the actual file there. This is rarely the issue. Usually it's downloading and its failing since it thinks its the wrong one.
3. Close the toolset with a saved module. Work in directory mode so you can see dates on the files.
4. Open toolset, open module, prep client files.
5. Save module, close toolset.
6. Open toolset, prep server files.
7. Save module, close toolset.
8. Compare dates on the xml files in your module folder, campaign folder, etc with corresponding xml files in your prepped files folder. If they are not the same, copy the files manually. Check that file dates on lzma you deleted just updated in the prepped folder as well, if they are missing or not a new date, you likely are staging to another folder you don't know about. ( look in toolset prefs and compare the paths involved )
9. Carefully upload to the server, doublechecking dates again.
10. Restart the server ( this is a HUGE thing people over look, if you don't do this it still is using the old xml files )
11. Test it again ( if it's still an issue, review the logs and see if there is a new problem, if it's repeating either try deleting the xml files or hopping on IRC and asking for help )
The above for the most part catches almost all problems. Generally the person involved takes a lot of coaxing to get them to undertake the process "since they already tried that", but the issue is the details and most people are having a problem because they are overlooking something. The ADL is not that user friendly for the PW admin, but then it's very user friendly for the end user. Grinning fool if we had another patch could easily fix the issues which cause the above problems.
We have quite a bit of access to the ADL via DLL's right now, so those things are fixable, either as standalone, or via toolset plugin.
Modifié par painofdungeoneternal, 28 juillet 2011 - 11:42 .
Retour en haut
I appreciate your response.
