The_Kiiiing
-
Posts
2,664 -
Joined
-
Last visited
-
Days Won
32
Content Type
Profiles
Warranty Claims
Downloads
Forums
Store
Services
Downloads Plus Support
DOWNLOADS EXTRA
Reels
Everything posted by The_Kiiiing
-
The problem is fixed now- 1,163 comments
-
- 2
-
-
- #loot
- #customloot
- (and 13 more)
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.9
-
Images should work again now
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.9
-
Should be fixed now
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.9
-
Should be fixed now
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.9
-
Should be fixed now
-
I will fix this problem with the next update
- 1,163 comments
-
- 3
-
-
- #loot
- #customloot
- (and 13 more)
-
Changed Status from Pending to Work in Progress
-
I will fix the bug with the next update
-
Changed Status from Pending to Work in Progress
-
There are several problems regarding stacking in this version. I am currently working on an update to fix these problems.
-
Changed Status from Pending to Work in Progress
-
First of all you don't need to remove your data file if there is a new version. If you do so, your loot configs will be gone. This error should be fixed with the new version which will come in a few days.
-
Changed Status from Pending to Work in Progress
-
This is because the site where the images are hosted is currently down. I will release an update in a few days that should fix this problem
-
What did you do before that error came up?
-
It is applied to every loot container including inventory and storage.
- 1,163 comments
-
- 1
-
-
- #loot
- #customloot
- (and 13 more)
-
Changed Status from Pending to Closed
-
Your old loot config should still be there after the update. To be 100% save make sure to have a backup of the data/Loottable folder.
-
Your old loot config should still be there after the update. To be 100% save make sure to have a backup of the data/Loottable folder.
-
Changed Status from Work in Progress to Closed Changed Fixed In to 1.0.8
-
Should be fixed now
