sal_vager

I think they are both an international standard symbol for electrical hazard. The square symbol is usually used on vehicles, while the triangle is used for signs.

I find this happening sometimes, it's almost like 1 pixel of mouse movement is too far, have you tried moving the view to see if it has an effect?

The fixed addon rules are now live, modpacks are not banned but packers (and modders including dependencies) must provide information on every addon they include. These rule changes are not retroactive so existing mods are not affected. The poll is now closed, if it does become necessary to ban modpacks as described in the addon rules then that can be done at a later date. Thread is now closed.

Starting to get into the "too much work for modder" territory. But I guess for lists of included dependencies/add-ons it'd be like this.

I think I already did.

Great! If it happens again maybe consider making a shortcut to the prefs file folder, to make removing it easier.

I don't think there's anything to be gained by saying modpack X is for version N only, it may still work, but it would be important for users to know the versions of the mods inside it.

Something to avoid though is making more work for the modders, ideally the common practices amongst modders would continue, such as KSP version numbers in the thread titles, without forcing these things.

Yes that's why the full list with authors names, urls and licenses must be in the OP and in the pack. Edit: Note to self, find less lazy moderators...

"No spoilers" might be a little too picky, modpacks can be really large.

I'll have to review it, and whether that rule is correctly worded, btw it means mods you install in KSP, not programs that are externally run, I forget which yours is. This seems fine, but why without the spoiler? Edit: It's now "Add-ons or packs must document all add-ons, plugins and dependencies they contain, including their authors and links to the original work, in the download and in the download location."

The rule is not retroactive, and the changes made to RO are significant, RO would not be affected. Best kind! The more addons in a pack, the more work the packer must endure, failure to do so results in removal and further action if it persists. Having all licenses means that packs will still have those licenses even if the packer disappears, I may also add that links to the original works must also be provided. Phew. Edit: Also, generic addon install instructions and how to get help will be a new sticky thread.

Well, naughty you, this rule has been in the addon rules for a very long time, since the time they were first posted actually and was introduced to prevent dodgy plugins from putting files in odd locations. Well, the rule does state... So if they are all yours or all maintained by you maybe we need a new word for it.

I believe modders already do this, so no extra work for them.

Well, the idea is you license each add-on in the pack, or all with the same license, the issue being that I do not want to see one modpacker claiming to own a particular style or content of a modpack, trying to prevent others from releasing a similar pack.

Hehe, okay I'll paste them here. ---------------------------------------------------------------------- General Add-on posting rules 0. Definitions Add-on. Original or derivative work intended to expand another work by adding or replacing files Dependency. An add-on included with an add-on that is required for it to function, license or permission permitting. Pack. An archive (zip, rar etc) containing multiple add-ons other than those of the submitter, which can be replaced with a list of contents, links to original works, or automated installer script to create the same end result. Or to which any changes: Can be removed and the pack remains viable. Are insufficient to create a new derivative work. Are suspected to exist in an attempt to bypass this definition. 1. Licenses All add-ons, dependencies and packs that are posted on the services maintained by Squad that serve the KSP Community (such as this forum and Curse) must be accompanied by a license for each add-on contained therein, that regulates what other users can do with the copyrighted material. These licenses must be made available in both the download file as a readme or license text, and in the location the user downloads from (such as a forum post or a Curse listing). Packs of add-ons cannot be licensed as a whole and no ownership of a pack of add-ons is permitted. 2. Forbidden content Add-ons may not violate the Community Rules. 3. Mandatory content Add-ons or packs must document all add-ons, plugins and dependencies they contain, including their authors, links to the original work and version in the download and in the download location. Add-ons or packs that require permission for any content must include these statements of permission. Plugin specific rules 4. Source code All plugins that are made available on the services maintained by Squad that serve the KSP Community must have their source code be made publicly available. This can be achieved by posting it on a public code repository and linking this repository in every location you offer the plugin for download. Including the source code in the download file itself instead of hosting it on a public code repository also satisfies this requirement. 5. Forbidden code Your plugin may not: Edit, delete, or create files outside of the KSP installation folder and the operating system temporary storage locations; Introduce anything in the game meant for profit. This includes ads and donation buttons; or Remove or modify Squad logo's or copyright notices. 6. Contacting another network or computer system Add-ons that contact another network or computer system must tell users exactly what it's sending or receiving in a clear and obvious way in all locations it is offered for download. 7. Gathering of personally identifiable information Add-ons that gather personally-identifiable information and send this information to another network or computer system must: Provide the user with an opt-in system within the game that requires the user to agree unambiguously with the information gathering and sending before any such information is sent; this opt-in system must inform the user of the goal and extent of the information gathering; Provide the user with an option in the AppLauncher to disable the data gathering that is visible in at least the Space Center scene; and Grant a user the option to review and remove all personally identifiable information that is within control of the person who maintains the add-on. For the purpose of this rule, personally identifiable information does not include information that is sent beyond the control of the add-on author when establishing a connection to another network or computer system, such as IP addresses, so long as this information is not coupled and stored with the other gathered information. Personally identifiable information is defined as information that can be linked to a specific user. 8. Legal boundaries You may not decompile, modify or distribute any of the .dll files or other files KSP comes with beyond content of the GameData folder. Follow the EULA. For assemblies, you may only use exposed public or protected members of classes, and you may not examine the code within any member. Third party applications 9. Application of the add-on rules With the exception of the first bullet point in rule 5, these rules equally apply to any stand-alone applications made available on the services maintained by Squad that serve the KSP Community. --------------------------------------------------------- Most of this is the same but it expressly permits what @SolidJuho is doing, while allowing moderators to remove anything less without having to waste time or bandwidth.

Would you all perhaps like to see the changes to the addon rules I am working on?

The problem packs don't make it past the moderators, or don't survive for long and are reported and removed, but each one involves lots of work dealing with the member, the licenses etc. We really don't have any modpacks as I would define them on this site.

Doesn't matter what your licence is if mod repackers can do what they please off-site, so you may as well choose a license that you want your work to be enjoyed by here. Mod repackers who are respectful can work, I've already mentioned one twice, he is willing to go the extra mile and I thank him for that. The current ann-on rules can change a little though, to make it easier for the moderator team to remove low effort mod packs, while allowing the kind where due diligence has been observed. A ban is a last resort, but it is on the table if it is necessary to prevent the kind of mod repacking that several respondents to this thread have expressed as unwelcome.

Squad has contracted Blitworks to produce new console versions, this will take time, please be patient

Hi @jokiab, please see the first posts for news if any

You confused me with this then, By all means, see if there is any change. Also, try resetting KSP's settings, do this by deleting the settings.cfg in the games folder, and to ensure there's no unwanted settings also delete the prefs file from /home/username/.config/unity3d/Squad/Kerbal Space Program/

Still works, see Stone Blues post.

I would actually call this a mod in its own right, though it targets other mods instead of the stock game, much like how Kopernicus configs can provide new planets but require Kopernicus to be installed. Work was actually done to produce these files and the mod doesn't exist if those files are removed, they are far from minimal, and are not included with the sole purpose of conforming to a definition. This isn't the kind of work that could be replaced with a list of mods for example.

Sorry guys but the moderation team has received several requests for closure of this thread. So I'll be closing this under rule 2.2H The submitter has failed to provide any proof of concept and no factual basis for the claims made have been presented. As such it fails to qualify as either science or spaceflight, and belongs on another forum.