I just started using WT# 2.2.1 and I think it is great to be able to manage and modify my Borderlands Avatars' stats, weapons and items. Thanks to WT# and the development team, WT# is a powerful tool enabling everyone to customize and manipulate the Borderlands environment. Brings me back to my days of hacking and hex editing.
I have been on Borderlands big time building all four classes up in preparation for Borderlands GOTY and Borderlands 2. This has led me to do some Backpack Management as I have built 4 fairly large collections of guns, mods, shields, etc.
I have successfully used WT# to modified several weapons for personal preferences (add sights/scopes, add elemental effects and elemental multipliers, etc).
However (this is the problem I am submitting) when I export "All (Weapons) to XML" or export "All (Items ) to XML" and then try to Import "All (Weapons) from XML" or Import "All (Weapons) from XML" a quirky problem occurs.
The Actual Export/Import Process works with the Most of Raw Data showing in the proper places, however if there are similar items/weapons with slightly different characteristics, all the Items show up with exactly the same characteristics
i.e.
Items Before Export in Weapons Tab Items After Import in Weapons Tab
This has happened with several items that I have been tinkering with to improve my session time in Borderlands (i.e. Several Caustic Snipers that I have been tinkering with to familiarize myself with Weapons Construction and Improvements.
Is this one of the known problems with import/export that I have seen mentioned on this forum? It does kind of remind me of an Open Source Project with several "cooks" working together.
My Setup is as follows:
MS Windows Vista Business with .Net Framework 3.5 sp1
WT# 2.2.1
Xbox 360 V2 and Borderlands (I assume pre patch 1.3 b/c it is the Xbox release from 1-2 years ago)
Modio
Thanks in Advance for a great product that had made my Borderlands experience so much better.
JRO
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a known problem with WT# 2.2.1.102. The problem stems from the way WT# 2.2.1.102 loads data for all the weapons BY NAME from the XML files. As you have seen, this causes issues if there are two items with the same name. Whoever originally wrote the code understood that this was a problem so the locker renames the items in such a way that they will not have the same name before it saves them to an XML file by adding (Copy #) to additional items with the same name. Unfortunately, the export function in the Weapon tab does not do this so even though exporting the items exports all the data into the XML file just fine, they can't be imported properly because they have the same name.
In the experimental revision (rev 170 is the latest experimental build which can be found in the Experimental folder in the files area) this bug was fixed by an extensive rewrite of the way WillowTree# keeps track of items internally. Nothing is stored by name anymore. I wanted to provide better item naming and inventory tree categories along with repairing several bugs in the import and export and none of that was possible with the way the data used to be stored. I believe the XML file you export from WT# 2.2.1.102 will load fine in experimental revision 170 since this bug has been squashed.
I won't be fixing this bug directly in WT# 2.2.1.102 because I don't have a license to develop with the DevComponents DotNetBar commercial library that it uses. Any future development I do of WT# will be on the experimental revision in which I removed the DotNetBar library. It lacks the polished look of the DotNetBar version since DotNetBar is a great library which provides a lot of GUI support like color themes and the office-like ribbon UI that aren't available in Windows Forms, but it does have a great deal more functionality and I hope I have fixed most of the bugs with importing and exporting which is either buggy or inconvenient to use in many places in WT# 2.2.1.102. I have not pushed the experimental version as a new release yet because I have rewritten a lot of code (both GUI and internal functionality) and it hasn't been adequately tested to make sure it all works as it should. Since WillowTree# has an update version notification I don't want people to become annoyed by a notification of a new version which may fail in some simple way that WT# 2.2.1.102 will not.
If you prefer to use WT# 2.2.1.102, I wrote a small utility program today that you can use to "fix" an exported xml weapon file in a way that the items will be able to load back into WT# with proper stats. It will parse the XML file and rename duplicate-named items. You can find it in the support folder in the file area:
Due to a bug with SourceForge's file manager related to having a file folder named "support", the above file link is giving me a 404 error. I've filed a ticket on the issue and made another folder named "support_files" and re-uploaded the file. Here's the new link:
Greetings,
I just started using WT# 2.2.1 and I think it is great to be able to manage and modify my Borderlands Avatars' stats, weapons and items. Thanks to WT# and the development team, WT# is a powerful tool enabling everyone to customize and manipulate the Borderlands environment. Brings me back to my days of hacking and hex editing.
I have been on Borderlands big time building all four classes up in preparation for Borderlands GOTY and Borderlands 2. This has led me to do some Backpack Management as I have built 4 fairly large collections of guns, mods, shields, etc.
I have successfully used WT# to modified several weapons for personal preferences (add sights/scopes, add elemental effects and elemental multipliers, etc).
However (this is the problem I am submitting) when I export "All (Weapons) to XML" or export "All (Items ) to XML" and then try to Import "All (Weapons) from XML" or Import "All (Weapons) from XML" a quirky problem occurs.
The Actual Export/Import Process works with the Most of Raw Data showing in the proper places, however if there are similar items/weapons with slightly different characteristics, all the Items show up with exactly the same characteristics
i.e.
Items Before Export in Weapons Tab Items After Import in Weapons Tab
Krom's Sidearm (No sight) Krom's Sidearm (Sight 5)
Krom's Sidearm (Sight 2) Krom's Sidearm (Sight 5)
Krom's Sidearm (Sight 4) Krom's Sidearm (Sight 5)
Krom's Sidearm (Sight 5) Krom's Sidearm (Sight 5)
This has happened with several items that I have been tinkering with to improve my session time in Borderlands (i.e. Several Caustic Snipers that I have been tinkering with to familiarize myself with Weapons Construction and Improvements.
Is this one of the known problems with import/export that I have seen mentioned on this forum? It does kind of remind me of an Open Source Project with several "cooks" working together.
My Setup is as follows:
MS Windows Vista Business with .Net Framework 3.5 sp1
WT# 2.2.1
Xbox 360 V2 and Borderlands (I assume pre patch 1.3 b/c it is the Xbox release from 1-2 years ago)
Modio
Thanks in Advance for a great product that had made my Borderlands experience so much better.
JRO
This is a known problem with WT# 2.2.1.102. The problem stems from the way WT# 2.2.1.102 loads data for all the weapons BY NAME from the XML files. As you have seen, this causes issues if there are two items with the same name. Whoever originally wrote the code understood that this was a problem so the locker renames the items in such a way that they will not have the same name before it saves them to an XML file by adding (Copy #) to additional items with the same name. Unfortunately, the export function in the Weapon tab does not do this so even though exporting the items exports all the data into the XML file just fine, they can't be imported properly because they have the same name.
In the experimental revision (rev 170 is the latest experimental build which can be found in the Experimental folder in the files area) this bug was fixed by an extensive rewrite of the way WillowTree# keeps track of items internally. Nothing is stored by name anymore. I wanted to provide better item naming and inventory tree categories along with repairing several bugs in the import and export and none of that was possible with the way the data used to be stored. I believe the XML file you export from WT# 2.2.1.102 will load fine in experimental revision 170 since this bug has been squashed.
I won't be fixing this bug directly in WT# 2.2.1.102 because I don't have a license to develop with the DevComponents DotNetBar commercial library that it uses. Any future development I do of WT# will be on the experimental revision in which I removed the DotNetBar library. It lacks the polished look of the DotNetBar version since DotNetBar is a great library which provides a lot of GUI support like color themes and the office-like ribbon UI that aren't available in Windows Forms, but it does have a great deal more functionality and I hope I have fixed most of the bugs with importing and exporting which is either buggy or inconvenient to use in many places in WT# 2.2.1.102. I have not pushed the experimental version as a new release yet because I have rewritten a lot of code (both GUI and internal functionality) and it hasn't been adequately tested to make sure it all works as it should. Since WillowTree# has an update version notification I don't want people to become annoyed by a notification of a new version which may fail in some simple way that WT# 2.2.1.102 will not.
If you prefer to use WT# 2.2.1.102, I wrote a small utility program today that you can use to "fix" an exported xml weapon file in a way that the items will be able to load back into WT# with proper stats. It will parse the XML file and rename duplicate-named items. You can find it in the support folder in the file area:
http://sourceforge.net/projects/willowtree/files/support/WTXmlFix.zip
Due to a bug with SourceForge's file manager related to having a file folder named "support", the above file link is giving me a 404 error. I've filed a ticket on the issue and made another folder named "support_files" and re-uploaded the file. Here's the new link:
http://sourceforge.net/projects/willowtree/files/support_files/WTXmlFix.zip