Remove ability to blueprint enemy ships while in survival mode #534
Conversation
…f the ship belongs to the player, or the ship's owner is in the player's faction. Will work regardless of ownership if the player is in creative mode.
|
It'd be best to have some facility to be able to scan ships and make a blueprint, but that is a lot of work for a PR, alternatively we could use a mod API for ship blueprints, read existing ones, add new ones... maybe not edit and remove though. |
|
As someone who plays/played a lot of MP survival and has used this trick to pick apart enemy bases I agree that blueprinting should be restricted like you have it. @THDigi also has a good point about implementing some sort of balanced alternative but I don't think that should stop this PR from going through. |
|
Yes this PR is the first critical step. |
|
I think you should add a check as to if the player is an admin too? |
|
"Allow blueprinting unowned grids" should be an option set during server/world creation. |
|
@kennyrkun I don't know if keen still actively reviews these PRs / issues. Also, in the data model for grids, I don't believe that a grid has a owner, (own-able blocks do). I could be wrong about both of those though. |
|
Keen hardly looked at this even when it was being maintained. The GitHub is now only here for reference and Keen doesn't do anything with it at all anymore. A grid's owner is determined by who owns the majority of ownable blocks on the grid, as a matter of fact I think this feature is already implemented in the game. |
|
Thanks @Jimmacle. |
|
@mccorkle I know they don't look at it, but I do. I'm trying to port the code to C++ so I can modify the game myself, and make my perfect world. |
|
SE is not open source and you're not allowed to use its code for your own purposes, including porting. |
|
@Jimmacle I'm not even part of this conversation, but if it's not open source, why the fuck is it on GitHub? Have some decency and at least pay for a private repository, or host it somewhere else that has free private repositories. Having a non-open source project in a GitHub public repository is outright asinine. It opens a whole world of problems, including unintentional misuse of the source code. |
|
I'm not gonna disagree, I don't know why this is still up considering it's not even up to date anymore. I'm just letting him know so he can avoid potential legal trouble, but in general you should read the license supplied with the code, and if one isn't there assume you have no rights to use it. |
This is incorrect. They can do whatever they want privately with the code including porting. They're just not allowed to redistribute anything. |
|
EULA Quick Section 5:
I think that what I want to do is okay. I don't want to be a better Space Engineers or anything, and I don't want to discredit Keen. I just want to make the perfect game for myself. |
|
Good luck @kennyrkun. I'd recommend forking this and tracking issues over on your fork (as you would have the power to fix issues there). Also, worth noting, I've heard that the devs at Keen hang out on the Keen discord. Asking questions and getting help with your project might be better served there (https://discordapp.com/invite/KeenSWH) |
|
I've been in the Keen discord since it was started, and I forked this repo a few days ago. I just have to actually get started. I hope I can learn from it and actually figure out how to make a game, so one day when I grow up I can work with the big boys in Unreal or Source 2 :D |
Initial issue: Player were able to get the blueprint of an enemy ship (Ctrl+B) which they could then project, build in creative and explore for weaknesses.
Fix: Players will not be able to get the blueprint of a ship if they are not the owner, or if the owner is not in their faction. Players will still be able to get blueprints of a completely neural ship, and players will be able to blueprint any ship while in creative mode.