Permission denied error?

[subtledoctor]

I'm seeing a weird error message with the latest version of a mod:

ERROR: Sys_error("override/: Permission denied")

I should say, *I'm* not seeing it, but some players are seeing it. It installs perfectly well on my system, which is making this hard to figure out.

EDIT - gah, this was just a typo that happened to cause no symptoms on macOS. Fixed now, move along, nothing to see here.

[Jarno Mikkola]

(The point of doing the .ini file that way is...

Or you could surely ask the settings you set there in the install phase, it's not like this is anything else ... except HARDER to do that.

 

Speaking of permissions, how does the MacOs run the fnp install ? Could it have something to do with it ? Not that that's likely..

The Windows 10 can throw things like the above if the game is installed to a non players profile folder on the C drive, aka this everyone should know that try to mod their BG2 games, in Win10. Cause the Win10 tries to protect the end usercorporate interests.

 

Any by the by, can't you just include the file from the mod folder, not the override folder ? Cause that's pure BS in the override folder.

 

AKA:

ALWAYS
INCLUDE ~faiths_and_powers/d5_fnp_settings.ini~ 

[subtledoctor]

how does the MacOs run the fnp install ? Could it have something to do with it ? Not that that's likely..

The Windows 10 can throw things like the above if the game is installed to a non players profile folder on the C drive, aka this everyone should know that try to mod their BG2 games, in Win10. Cause the Win10 tries to protect the end usercorporate interests.

 

Actually it was an OS issue, at least with diagnosing the error - there was a trailing slash in a COPY command:

COPY_EXISTING ~%spell%.spl~ ~override/~

That actually works fine in macOS because it can deal with trailing slashes after directory names. But a trailing slash - a trailing forward-slash - in Windows blows up the command. So I couldn't reproduce the bug on my Mac install.

 

Any by the by, can't you just include the file from the mod folder, not the override folder ? Cause that's pure BS in the override folder.

My understanding is (and correct me if I'm wrong), if a player changes that file, BWS will detect a modified mod (size check and whatnot) and download the mod over again and overwrite the player's changes. I'm trying to work around that annoying aspect of BWS and let players actually use a settings file.

 

All the .ini file contains is:

DEFINE_ACTION_MACRO d5_blah BEGIN
   OUTER_SET d5_variable = 1
END

[Jarno Mikkola]

My understanding is (and correct me if I'm wrong), if a player changes that file, BWS will detect a modified mod (size check and whatnot) and download the mod over again and overwrite the player's changes.

Well, if the file size is different, then the BWS can if the install person want to, have a setting "that uses the currently downloaded" OR "the newest most updated version of the mod" that goes according to the current table of file sizes... in the best cases where download link also possesses the file size info, that the BWS can access to, it just uses that. In the worst, the BWS itself comes with the recorded file size information, which is then used.

But that's not to say that you can't ask the question of which option you want to install in the component (name).

 

And if you use macros to do most things, you can include all those in the ALWAYS, Or in includes. And have weidu just run them according to the sub component names.

Such as ... as I am not a poet, I'll use crude language, as it's finer for this, than not so crude language:

~Sarevok is a bad ass mother fucker~

~Sarevok is a bad mother fucker~

~Sarevok is a ass mother fucker~

~Sarevok is a bad ass fucker~

~Sarevok is a bad ass mother~

~Sarevok is a bad mother~

~Sarevok is a ass mother~

~Sarevok is a bad ass~

...

Aka the language itself has a point, you can name the component name to the exact option you want it to consist of. And not have a default setting somewhere deep inside the code NO ONE will ever even want to go look, let alone edit.

As in all your mod options should show up during the install, not scattered around the 178 files inside folders they probably shouldn't occupy. Or have you heard of the mod that went and made 15 other directories into your game folder during it's install, I am pretty sure you have an objection to that... and if not you, then every one of the BWS makers WILL.

 

Edit: Hah, finally we agree on something:

I am not sure which (non-existing) BWS problem you try to solve, but putting ini files into override is a pretty weird solution.

Why not do such a simple thing as to put *enable dual classing* as an install option? If selected, use your macro to set the variable. What does BWS have to do with it?