<VITAS[m]>
we should either fix them or remove at least the menu entry
<VITAS[m]>
yes i think that was the idea
<VITAS[m]>
give a list
<VITAS[m]>
we could offer on the fly zipping everything in one pack
<VITAS[m]>
i remember fears that mod authors wouldnt like it
<VITAS[m]>
but i think its ok
<VITAS[m]>
isnt that the rik with other downloads too?
<VITAS[m]>
im not responsible for every users action
<VITAS[m]>
i think it was about intended distribution channeles and repackaging
<VITAS[m]>
but still: ive no problem bunching zips into another or even unzipping them and reziping them for as long as every mods files are unaltered
<VITAS[m]>
my point is that by uploading files to spacedock a copyright owner grants the site the right to distribute them
<VITAS[m]>
zips are only a way to put folders into one file and not the copyrighted item iteself their content is
<VITAS[m]>
its about sending stuff arround
<VITAS[m]>
a user could also send individual mods arround
<VITAS[m]>
or ckan files
<VITAS[m]>
not my problem
<VITAS[m]>
and may i add that in some countries like germany its even legal
<VITAS[m]>
thers something called a private copy
<VITAS[m]>
you are allowed to copy even copyrighted material and lend it to a friend
<VITAS[m]>
so in the end: either we keep it or we remove the menu option
<VITAS[m]>
isnt very popular because most people didnt understand how it works or it didnt even work for them
<VITAS[m]>
if we keep it we have to fix it and maybe either rename it to reflect what its doing or change how it works
<VITAS[m]>
if i click modpack i expect a pack of mods not a list of bookmarks
<VITAS[m]>
i think its usefull
<VITAS[m]>
but we should make sure they work and are properly named
<VITAS[m]>
e.g. mod list
<VITAS[m]>
custom mod group will get long
<VITAS[m]>
but youll think of something
<VITAS[m]>
:)
<VITAS[m]>
bonus points for checking if all mods have ckan flags and then autogen a ckan file
<VITAS[m]>
ah ok
<VITAS[m]>
so we leave that for now :)
<VITAS[m]>
i would do: if all mods in a modlist are on ckan then autogen ckan file if not alert author of list
<VITAS[m]>
(and dont gen ckan file)
<VITAS[m]>
there are other uses than mp
<VITAS[m]>
yt, sharing with firends, twitch
<VITAS[m]>
HebaruSan: yes for sd to know if a mod is on ckan or not would be helpful.
<VITAS[m]>
we could even auto check the box if it is
<VITAS[m]>
and if he disables it ckan knows he doesnt want it to be
<VITAS[m]>
(so sd is sort of the ui for ckan)
<VITAS[m]>
((as in mod administration for authors)
HebaruSan[m] has joined #spacedock
<HebaruSan[m]>
Are modpacks still a thing on SD? I tried creating one but it seems to just freeze and I can't find a list of them either.
<HebaruSan[m]>
I got it to work better on alpha
<HebaruSan[m]>
Enough to investigate an issue a little bit
<HebaruSan[m]>
What are they supposed to do? Is there any capability for mass-download or get a .ckan file or something?
<HebaruSan[m]>
I just see many separate Download buttons
<HebaruSan[m]>
I mean if it's just a matter of batching a bunch of ZIPs into one ZIP on the fly and not generating anything permanent or uploading elsewhere, it seems like it should be fine
<HebaruSan[m]>
I guess there's a risk a user might save the ZIP and send it to others, and it would become the bad kind of modpack
<HebaruSan[m]>
Well on the one hand you have the risk that a user downloads 20 ZIPs, unzips them, repackages them in his own ZIP, and sends it around.
<HebaruSan[m]>
On the other hand you have a tool on a web site doing most of that for him.
<HebaruSan[m]>
I'm not so much worried about the legal side. Go post on the forums how much you like modpacks if you want to know what I'm thinking about.
<HebaruSan[m]>
Stop fixating on legality
<HebaruSan[m]>
Do we know how many rows there are in that table in prod?
<HebaruSan[m]>
Yeah, same
<HebaruSan[m]>
But if some folks are finding them useful as-is, maybe it's OK to leave it alone
<HebaruSan[m]>
It does show the latest version of each mod in one screen, maybe some people use them to look for updates without clicking 100 pages
<HebaruSan[m]>
Group?
<HebaruSan[m]>
Custom Group?
<HebaruSan[m]>
We'd need a new webhook for that, but still it wouldn't be impossible
<HebaruSan[m]>
(Somebody needs to translate SD's mod ids to CKAN module identifiers)
<HebaruSan[m]>
It would mess up sometimes, though, when multiple modules share one download
<HebaruSan[m]>
Maybe not enough to matter
<HebaruSan[m]>
Also the question of what to do about mods not on CKAN could get thorny
<HebaruSan[m]>
Do you say "Download .ckan file for this modpack here!" if several of the mods aren't in it at all?
<HebaruSan[m]>
Now I'm wondering if we should do a reverse import to set `mod.ckan=True` for mods where the author didn't click the checkbox on SD but instead asked us to add it separately alter
<HebaruSan[m]>
Now I'm wondering if we should do a reverse import to set `mod.ckan=True` for mods where the author didn't click the checkbox on SD but instead asked us to add it separately later
<HebaruSan[m]>
That happens once in a while
<HebaruSan[m]>
OK, I'll have a think about best ways to do that
<VITAS[m]>
had a play with bootstrap and adminlte3 what do you think? worth developing in a template replacement for sd?
<VITAS[m]>
so?
im52kde has quit [Network ban]
VITAS[m] has quit [Network ban]
HebaruSan[m] has quit [Network ban]
RockyTV[m] has joined #spacedock
<RockyTV[m]>
it looks good
<RockyTV[m]>
also, regarding modpacks: I had an idea (probably what <span class="d-mention d-user">HebaruSan</span> did), that when creating a modpack you can choose mods on the website. and we could add a new property on mods, something like `allow-modpack` or so. if the mod has this flag set to true, users can add this mod to their modpack, otherwise they can't.
<RockyTV[m]>
and do we have any problems with our current multigame implementation?