Game_Engine/Licensing (content todo) #42992
Labels
No Label
Meta
Good First Issue
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Eevee & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds, Tests & Devices
Module
Python API
Module
Rendering & Cycles
Module
Sculpt, Paint & Texture
Module
User Interface
Module
VFX & Video
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Information from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-manual#42992
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
There are multiple issues on the game engine / licensing .
It appears that the topic is partially covered in section "So I can make games without having to worry about the GPL, right?" of http://www.blender.org/support/faq/
I suggest that the following text is used instead (check for factual correctness required by somebody who knows Blender better than I do):
Restrictions apply to games made with the Standalone Player , as Blender is licensed under the copyleft license GNU GPL.
You own your work made with Blender but when you create an executable for your game, part of the Blender Game Engine gets copied into it, making it a derivative of Blender. GPL requires that derivative to be GPL-licensed.
Instead, you can bundle the Standalone Player and your .blend game without combining the files. Using Game Actuator , enables a basic .blend game file to start. By making a basic file which contains an "Always" sensor to run, and allowing this to activate a "Game" actuator to load and run the full content of your game, this gets round the problem.
The .blend file is not encrypted and readable by anybody who owns the game. You still control what people are allowed to do with your .blend by choosing the terms under which you distribute your game but people will easily be able to study and modify their copy of it.
Changed status to: 'Open'
Added subscriber: @qubodup
Added subscriber: @JulianEisel
Hey @qubodup,
this is our Blender bug tracker, not our Blender documentation suggestions tracker ;). So for tasks like this please do a couple of things different in future:
Removed subscriber: @JulianEisel
Added subscribers: @JulianEisel, @fsiddi, @pablovazquez, @Ton, @Sergey
@JulianEisel, broken links are really bad, it's not a todo but thing to be fixed.
@fsiddi or @venomgfx, can you please fix the links?
@Ton, can you please look into the feedback about licensing?
Oh dear, that wiki page is a mess, incorrect and not nice even. The page was written by unknown editors ( it's a wiki you know :)
A while ago tried to fix quickly some stuff on it, but after closer inspection I decided to rewrite it entirely.
http://wiki.blender.org/index.php/Doc:2.6/Manual/Game_Engine/Licensing
BTW: My general advise to anyone who uses the BGE is to not attempt to lock things up - it's a battle you never win anyway. Spreading Blender games just means you have to play by the GPL. If you don't like GPL, choose another game engine.
[documentation]to Game_Engine/Licensing (content todo)Changed status from 'Open' to: 'Archived'
Added subscriber: @ideasman42
@qubodup, this was indeed quite bad - I made some updates to the manual (so its at least not spreading mis-information).
https://www.blender.org/manual/game_engine/licensing.html
If you have corrections to make, please send us modified source file (View Page Source - top right)
Archiving this report.
Note, still not especially happy with this page, but think at least the main issues are cleared up. Further improvements can be made, but would prefer not to get into providing elaborate legal info in our manual.