Hugo at the Clever Clogs Tavern(blood and wine) does not regenerate the amount of gold that the mod allows, it's still capped at the base game level(750 crowns) after depletion/regeneration after a few days. He does start with quite a bit though.
*I used the Really Rich Merchants version of the mod*
Which, if any, version of Really Rich Merchants is supposed to work with The Witcher 3 version 1.31 ?
I've tried Really Rich Merchants 1.0, 1.04, and 1.041 and keep getting these errors:
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4028): 'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams' Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4047): 'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams' Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4048): 'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams' Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4224): syntax error, unexpected TOKEN_ELSE, near 'else' Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4311): syntax error, unexpected '}', expecting $end, near '}' Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4815): Could not find function 'NoticeAchievementProgress'
Warning [content0]engine\environment.ws(30): Global native function 'EnableDebugOverlayFilter' was not exported from C++ code. Warning [content0]engine\environment.ws(32): Global native function 'EnableDebugPostProcess' was not exported from C++ code. Warning [content0]engine\showflags.ws(11): Global native function 'DebugSetEShowFlag' was not exported from C++ code.
It's wrong to report about an error when it's an user mistake. Every modder have been annoyed by this, they prefer getting "help me please" rather than "fix your mod".
> Files updated for v4.04. Tested on v4.04 on Steam.
Updated and tested on v4.04 doesn't mean it doesn't _also_ work on earlier versions. If it said it _only_ works on v4.04 that would be different. But it doesn't.
the fact that you don’t understand that the game changes with new versions, as well as mods along with the game and why they are not compatible with old versions, is your problem and only yours
Blame Nexus for not separating the game into two, like they did for Skyrim. Whenever a mod mention "Next Gen", it intuitively means "ONLY for Next Gen".
Has "Next Gen" in the title of the mod and the mod page also has a tag saying "NEXT-GEN UPDATE COMPATIBLE"... but it not only works on Next Gen but also works on Classic (and helpfully says so in the file description).
Another case in point: DLC Names from the Path has a tag saying "NEXT-GEN UPDATE COMPATIBLE" ... does that mean **only** works no Next-Gen? No. In the file description it says "Compatible with Next-Gen version 4.0+ and Classic version 1.31/1.32"
There are tons and tons of other similar examples
Sometimes mods clearly say they're Next-Gen only... and that's helpful. Sometimes they explicitly say they're Classic only.. and that's helpful. Sometimes they explicitly say they work with both.. and that's helpful.
And sometimes they don't explicitly say any of the above, but maybe there's a "NEXT-GEN UPDATE COMPATIBLE" tag and nothing else... where you have to guess whether it works with Classic or not... and that's just annoying.
I really don't understand why the suggestion to simply and clearly say "Only works on Next-Gen" is taken as some kind of affront to modding, rather than as a good suggestion that would make life easier for everyone involved -- mod users and mod authors alike, since mod users would know exactly what they're getting and mod authors wouldn't have to field questions from confused users (especially new ones) who might not know that a mod with a "NEXT-GEN UPDATE COMPATIBLE" tag was intended by the mod author to signify that the mod only worked on Next-Gen (as is clearly not the case for many mods).
They are "Only Next Gen" whenever a mod doesn't mention anything about classic or was made very recently. Most modder today are making mods on Next Gen, and they can't say if they're classic compatible. Their mods are made for Next Gen in mind, so they release it with simply the tag "Next Gen Compatible" to better separate those "classic" catalogue that Nexus persist to keep them here.
The affront we have is against you. You didn't ask "is this mod compatible to Classic 1.32?" or test it and latter confirm it is not. No... you write a message saying it brings an error by assuming it is compatible to Classic 1.32 without any reflection. There are good comment and bad comment, and you did the latter. So please, for all the incredible works to everyone and making them pleasant life, don't report errors on Next Gen mods because you are on Classic 1.32.
It works. Make sure you use Script Merger and meditate 24 hours so you see his wallet refill up. [EDIT] I test, and it refills with much more money than vanilla.
From my testing, It works on Bram and he refill with much money. Make sure you use Script Merger and meditate more than 24 hours so you see his wallet refill up.
It works on Bram. Make sure you use Script Merger and meditate 24 hours so you see his wallet refill up. [EDIT] I test and it refill with much more money than vanilla.
68 comments
*I used the Really Rich Merchants version of the mod*
I've tried Really Rich Merchants 1.0, 1.04, and 1.041 and keep getting these errors:
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4028):
'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams'
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4047):
'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams'
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4048):
'ITEM_SET_TAG_NETFLIX' is not a member of 'handle:W3GameParams'
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4224): syntax error, unexpected TOKEN_ELSE, near 'else'
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4311): syntax error, unexpected '}', expecting $end, near '}'
Error [mod0000_mergedfiles]game\components\inventorycomponent.ws(4815): Could not find function 'NoticeAchievementProgress'
Warning [content0]engine\environment.ws(30): Global native function 'EnableDebugOverlayFilter' was not exported from C++ code.
Warning [content0]engine\environment.ws(32): Global native function 'EnableDebugPostProcess' was not exported from C++ code.
Warning [content0]engine\showflags.ws(11): Global native function 'DebugSetEShowFlag' was not exported from C++ code.
Also, if a mod errors out I see absolutely nothing wrong with reporting that to the mod author.
It's wrong to report about an error when it's an user mistake. Every modder have been annoyed by this, they prefer getting "help me please" rather than "fix your mod".
I can see nothing in the description that says this only works with Next Gen.
Updated and tested on v4.04 doesn't mean it doesn't _also_ work on earlier versions. If it said it _only_ works on v4.04 that would be different. But it doesn't.
Whenever a mod mention "Next Gen", it intuitively means "ONLY for Next Gen".
That's simply not true for a lot of mods.
Case in point: Grammar of the Path - Next Gen Enabled
Has "Next Gen" in the title of the mod and the mod page also has a tag saying "NEXT-GEN UPDATE COMPATIBLE"... but it not only works on Next Gen but also works on Classic (and helpfully says so in the file description).
Another case in point: DLC Names from the Path has a tag saying "NEXT-GEN UPDATE COMPATIBLE" ... does that mean **only** works no Next-Gen? No. In the file description it says "Compatible with Next-Gen version 4.0+ and Classic version 1.31/1.32"
There are tons and tons of other similar examples
Sometimes mods clearly say they're Next-Gen only... and that's helpful. Sometimes they explicitly say they're Classic only.. and that's helpful. Sometimes they explicitly say they work with both.. and that's helpful.
And sometimes they don't explicitly say any of the above, but maybe there's a "NEXT-GEN UPDATE COMPATIBLE" tag and nothing else... where you have to guess whether it works with Classic or not... and that's just annoying.
I really don't understand why the suggestion to simply and clearly say "Only works on Next-Gen" is taken as some kind of affront to modding, rather than as a good suggestion that would make life easier for everyone involved -- mod users and mod authors alike, since mod users would know exactly what they're getting and mod authors wouldn't have to field questions from confused users (especially new ones) who might not know that a mod with a "NEXT-GEN UPDATE COMPATIBLE" tag was intended by the mod author to signify that the mod only worked on Next-Gen (as is clearly not the case for many mods).
Most modder today are making mods on Next Gen, and they can't say if they're classic compatible. Their mods are made for Next Gen in mind, so they release it with simply the tag "Next Gen Compatible" to better separate those "classic" catalogue that Nexus persist to keep them here.
The affront we have is against you. You didn't ask "is this mod compatible to Classic 1.32?" or test it and latter confirm it is not.
No... you write a message saying it brings an error by assuming it is compatible to Classic 1.32 without any reflection. There are good comment and bad comment, and you did the latter.
So please, for all the incredible works to everyone and making them pleasant life, don't report errors on Next Gen mods because you are on Classic 1.32.
Even when using script merger, the slot mod overrides the merchant mods
Any idea?
if ( EInventoryFunds_Avg == fundsType ){AddMoney( (int)( 150 * 改一个你认为合适的数 * GetFundsModifier()) );}
[EDIT] I test, and it refills with much more money than vanilla.
Other than improving graphics, I did not install any other mods.
It's very disappointing.
[EDIT] I test and it refill with much more money than vanilla.