And we know Microsoft and Sony will never ease up on those limits because that's the whole point of their little walled gardens.
While there are certainly a handful of modders who are trying to 'punish' consoles or console players I wonder how many of them truly cannot be migrated because of those limitations. Maybe something changed in FO4 (I suspect not, but don't want to presume) but in NV and Skyrim easily 90% of the mods I used required the script extender, and the lack of a script extender on consoles is a result of the limits of the flexibility of the platform, not because some modder is too lazy or too spiteful to make it work on consoles. However I do wonder just how far modding can really go on consoles. The creation kit update also prepares it for PS4 mods, which should be coming out over the next month.Ĭlick to expand.Apologies, I misunderstood the emphasis of your post. In theory, this means that Bethesda should be able to stamp out those who simply port PC mods that they didn't create. What this means for the layman is that Strictly Bethesda now has the ability to ban people from posting mods to Bethesda's official mod service (), requiring them to buy a new copy of Fallout 4 in order to continue posting mods. "Uploading mods to requires Fallout 4 ownership via a Steam-linked account," announced the company in a blog post. In an effort to curb this behavior, Bethesda has just released an update to its creation kit, which forces console modders to link up to a Steam account that also owns a copy of Fallout 4.
When Bethesda launched porting their work over to the Xbox One version of the game without giving the original creator credit. Prospective console modders must now link their creation kit to a Steam account that also owns a copy of Fallout 4. Bethesda Updates Fallout 4 Mod Tools to Prevent Piracy
0 kommentar(er)
