Steam Community :: Discussions

DayZ

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Discover the best community content

Get the most out of DayZ with Steam Workshop. Find and install user-created mods, or create your own and upload it directly to Steam.

Home

Discussions

About

Workshop> DayZ> All Discussions

Lana

17 Jun @ 4:56am

Перепаковка, или Репак - REPACKS

Братцы, я в модострое человек "сырой" и новый.

Объясните мне исходный смысл перепаковки?

Часто видела это в подписях к модам...
Кто-то разрешает перепаковку, кто-то нет.
Суть ее в чем?
Это грубо говоря, мод "вскрывают" и оттуда вытягивают нужные для своих нужд скрипты\конфиги и благополучно пристраивают их к своим модам\сборкам выдавая за свое?
Или это делают без вскрытия .pbo, и просто саму .pbo-шку добавляют уже к своему моду?

...И если первое, по сути, можно сделать и без разрешения "в тихую", то... зачем спрашивать? Культуры-вопроса ради?

Или я чего-то очевидного не понимаю в этой схеме?

Как можно по сути доказать, что в чужом моде именно твои наработки были использованы, если это все (как я понимаю) спокойно можно переписать в исходном конфиге, который пакует саму .pbo?

==
И да, мне гуглить лень, мне интереснее в живую у людей спросить

====================
Brothers, I am a "newbie" in mod-building.

Explain to me the original meaning of repackaging?

I have often seen this in mod signatures...
Some allow repackaging, some do not.
What is the "sense" of it?

Roughly speaking, they "open" the mod and extract the scripts\configs needed for their needs from there and happily attach them to their mods\assemblies, passing them off as their own?

Or do they do this without opening the .pbo, and simply add the .pbo itself to their mod?

...And if the first, in fact, can be done without permission "quietly", then... why ask? For the sake of culture-question?

Or am I missing something obvious in this scheme?

How can you essentially prove that your developments were used in someone else's mod, if all of this (as I understand it) can easily be rewritten in the original config that packs the .pbo itself?

==
And yes, I'm too lazy to "google", I'm more interested in asking people in person

< >

Showing 1-6 of 6 comments

Zimon

18 Jun @ 11:00am

Как можно по сути доказать, что в чужом моде именно твои наработки были использованы, если это все (как я понимаю) спокойно можно переписать в исходном конфиге, который пакует саму .pbo?
НИКАК
Как только ты выложил мод в workshop он стал общественным, и люди могут делать с ним всё что захотят!

_KC76_

18 Jun @ 8:22pm

Originally posted by Lana:
Братцы, я в модострое человек "сырой" и новый.

Объясните мне исходный смысл перепаковки?

Часто видела это в подписях к модам...
Кто-то разрешает перепаковку, кто-то нет.
Суть ее в чем?
Это грубо говоря, мод "вскрывают" и оттуда вытягивают нужные для своих нужд скрипты\конфиги и благополучно пристраивают их к своим модам\сборкам выдавая за свое?
Или это делают без вскрытия .pbo, и просто саму .pbo-шку добавляют уже к своему моду?

...И если первое, по сути, можно сделать и без разрешения "в тихую", то... зачем спрашивать? Культуры-вопроса ради?

Или я чего-то очевидного не понимаю в этой схеме?

Как можно по сути доказать, что в чужом моде именно твои наработки были использованы, если это все (как я понимаю) спокойно можно переписать в исходном конфиге, который пакует саму .pbo?

==
И да, мне гуглить лень, мне интереснее в живую у людей спросить

====================
Brothers, I am a "newbie" in mod-building.

Explain to me the original meaning of repackaging?

I have often seen this in mod signatures...
Some allow repackaging, some do not.
What is the "sense" of it?

Roughly speaking, they "open" the mod and extract the scripts\configs needed for their needs from there and happily attach them to their mods\assemblies, passing them off as their own?

Or do they do this without opening the .pbo, and simply add the .pbo itself to their mod?

...And if the first, in fact, can be done without permission "quietly", then... why ask? For the sake of culture-question?

Or am I missing something obvious in this scheme?

How can you essentially prove that your developments were used in someone else's mod, if all of this (as I understand it) can easily be rewritten in the original config that packs the .pbo itself?

==
And yes, I'm too lazy to "google", I'm more interested in asking people in person

"repacking" is just taking someone else's mod and making it yours, or adding it to a "pack" of mods to use on your server ..

If you actually extract the Mod and make changes then re-compile the mod, that is not "repacking" and does not cause the same problems as "repacking".

There are a couple problems with "repacking", aside from the "moral" aspect of having permission (yes, you need permission to distribute someone else's work that you have not altered, regardless of "giving credit").
1. Each time the original mod is updated, or breaks and needs repaired, you have to unpack and repack your "repack" with the fixed/updated version, or your server may end up breaking.
2. For the Player, there is a high chance that you end up having a bunch of "repacks" for different servers that each include the same mods, wasting your hard drive space by having duplicates of the same 5-20Gb of date .. If not repacked, the Player would only need to have that mod installed once for all servers that use it.

Lana

18 Jun @ 11:24pm

Okay... if it's so easy to "gut" someone else's mod, then what's the point .bikey .privatbikey xD ?
I thought that keys at least somehow protect authorship and your work

_KC76_

19 Jun @ 6:47pm

Originally posted by Lana:
Okay... if it's so easy to "gut" someone else's mod, then what's the point .bikey .privatbikey xD ?
I thought that keys at least somehow protect authorship and your work

The bikeys do not "encrypt" the mod. Bikeys are just a registration method for the server and client to agree that the files with specific names are the same files with those same names.

Unpacking a mod to inspect it's contents before using it on your server, is just good practice, so that you know that the mod does not contain malicious scripts which might get past Steam's basic scanning when uploaded.
- Unpacking and then editing/altering the mod is specifically an "allowed" action, based on Bohemia and Steam Workshop EULAs .. uploading your ALTERED mod means YOU now have some of your own Intellectual Property (your edits) in the mod package.
-- This is very different from just taking an existing mod and re-uploading it UN-altered.