Is Back to Anchorage 1_1 LOD-10720 broken? While checking depdndencies vortex shows EPERM: operation not permitted, stat 'C:\Users\masak\AppData\Roaming\Vortex\downloads\fallout3\Back to Anchorage 1_1 LOD-10720.zip' Error: EPERM: operation not permitted, stat 'C:\Users\masak\AppData\Roaming\Vortex\downloads\fallout3\Back to Anchorage 1_1 LOD-10720.zip' Prior Context: at Object.openAsync (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9424:27) at loop (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:1834:205) at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
I've messed around in the GECK, and got it so that you may fast travel from the areas within the mod. However, to post the ESP, I require the author's permissions.
That is not a rule or allowance, the mod is always their intellectual property. What YisahVasNarri can do though is upload a patch to make that possible.
An old thread but it's worth disabusing many modders and gamers of their misconceptions regarding rights & intellectual property:
This mod cannot own "intellectual property" - it's a Bethesda DLC and game, and Bethesda retain all copyrights. This sort of issue has been tested in courts over the years. Unless a mod is 100% original and can exist fully independent of a game (for example a standalone piece of artwork that doesn't use any Fallout reference or idea), a modder can't legally "own" any rights or intellectual property because ultimately their mods are an infringement of the game's copyright. I refer you to this external legal website: https://www.koburgerlaw.com/blog/2020/7/29/thinking-before-moddingplayers-dont-own-what-they-make
Now, Nexus and many other mod-hosting sites will have their own "house rules" against modders re-using/loading other modders' stuff without permission, but they are all different. My rule of thumb is always ask and, unless you get a refusal, carry on but give credit.
Totally INCORRECT. A 'mod' will usually combine both the IP of the game the mod mods, AND the original creative work of the modder. No legal mumbo jumbo from the game publisher, or pseudo legal nonsense from a so-called law firm changes this fact.
What does reduce a modder's rights is publishing their work, for free, on a site like Nexus. This implies a willingness by the mod author to have their work generally redistributed - and the modder or site saying otherwise carries little to no legal weight. However, this applies to redistribution UNCHANGED- only the modder can give permission for derivative versions to be created from the original mod.
Commercially, authorised fan created content based on an IP exists to boost the revenue of the IP owner - Bethesda doesn't have a generous bone in its cold corporate body- mods make Beth a LOT of money without a penny of direct revenue from said mods.
On the Nexus, issues of 'law' are not really the point- issues of 'community' are. The community of modders and the community of mod users. Good will and decency help avoid the ever threatened collapse of modder willing, especially in the light of never ending Bethesda greed that seeks to end free modding, and replace it with a commercial store based approach.
So appreciate modders by appreciating their rights- permission is required to use the author originated part of any mod, which is usually the only part of a mod of interest to those wishing to use a mod as something other than originally intended by the mod author. Again, the original work in a mod is the IP of the mod author, and NOT the IP of Bethesda. That Beth has the right to control the distribution of derivative works does not change this legal FACT.
Do you mean big red & white exclamation marks? Do you mean a DC vertibird? (iirc the device just triggers fast travel, when you activate it after going back outside the entrance).
This is a bit late but: Sounds like a load order issue/conflict. Try moving it down the order (or moving it up if you had it later, but always make sure it's after the game and dlc esm files. Did you toggle invalidation? - I've found that just having it on isn't good enough, you need to untick it then tick it again. Make a clean save in case you've just/recently uninstalled another mod. If it's some other conflict you could be out of luck unless you go through removing mods one by one - my total guess would be to try the uup patch, armor, and maybe enb or weather mods first.
I having a porblem with anchorage. I loaded the mod and everything works except for fast travel and merchant. I don't think the chinese remnants are respawning either, which sucks. Since fast travel isnt working I cant reach the artillery overlook. Please fix. Otherwise the mod is awesome! keep up the good work
Hi , I downloaded the 2 files and put them both in the right location , and anchorage is working but I can't fast travel and theres no merchants and ect. Ant tips please ? thanks
84 comments
Edit: Yeah im just a dummie i didnt look for the save, so yeah im ready to retake Anchorage
EPERM: operation not permitted, stat 'C:\Users\masak\AppData\Roaming\Vortex\downloads\fallout3\Back to Anchorage 1_1 LOD-10720.zip'
Error: EPERM: operation not permitted, stat 'C:\Users\masak\AppData\Roaming\Vortex\downloads\fallout3\Back to Anchorage 1_1 LOD-10720.zip'
Prior Context:
at Object.openAsync (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:9424:27)
at loop (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:1834:205)
at process.processTicksAndRejections (node:internal/process/task_queues:77:11)
This mod cannot own "intellectual property" - it's a Bethesda DLC and game, and Bethesda retain all copyrights. This sort of issue has been tested in courts over the years. Unless a mod is 100% original and can exist fully independent of a game (for example a standalone piece of artwork that doesn't use any Fallout reference or idea), a modder can't legally "own" any rights or intellectual property because ultimately their mods are an infringement of the game's copyright. I refer you to this external legal website:
https://www.koburgerlaw.com/blog/2020/7/29/thinking-before-moddingplayers-dont-own-what-they-make
Now, Nexus and many other mod-hosting sites will have their own "house rules" against modders re-using/loading other modders' stuff without permission, but they are all different. My rule of thumb is always ask and, unless you get a refusal, carry on but give credit.
What does reduce a modder's rights is publishing their work, for free, on a site like Nexus. This implies a willingness by the mod author to have their work generally redistributed - and the modder or site saying otherwise carries little to no legal weight. However, this applies to redistribution UNCHANGED- only the modder can give permission for derivative versions to be created from the original mod.
Commercially, authorised fan created content based on an IP exists to boost the revenue of the IP owner - Bethesda doesn't have a generous bone in its cold corporate body- mods make Beth a LOT of money without a penny of direct revenue from said mods.
On the Nexus, issues of 'law' are not really the point- issues of 'community' are. The community of modders and the community of mod users. Good will and decency help avoid the ever threatened collapse of modder willing, especially in the light of never ending Bethesda greed that seeks to end free modding, and replace it with a commercial store based approach.
So appreciate modders by appreciating their rights- permission is required to use the author originated part of any mod, which is usually the only part of a mod of interest to those wishing to use a mod as something other than originally intended by the mod author. Again, the original work in a mod is the IP of the mod author, and NOT the IP of Bethesda. That Beth has the right to control the distribution of derivative works does not change this legal FACT.
EDIT: Found it. Nevermind.