ModHQ 2.0

[Magick]

Need to adjust this to make it more obvious which file is the main download and which are optional files, adjust the UI a bit.

Shrink and indent the optionals, that are related to the main.

Also invert the colours in the ModHQ logo, as it is on here.
Helps distinguish the tabs per the icon then, too.

[Nooneatall]

Change the logo to goatse

[rusty_shackleford]

Need to adjust this to make it more obvious which file is the main download and which are optional files, adjust the UI a bit.

Awesome job.

I just came across something that might be of interest while you work on main and optional.
Wyll's of Toril for example has the option to change horns. Which is obviously optional. But to use the optional horn you have to download another mod, which is a dependency you need for the horn to work. I can't hardcode it as a dependency in the mod itself like usual and force a pop up because you can have multiple different base skin colours and which dependency you need is entirely based on the head you downloaded so its like this

MAIN: Neverwinter head
|_____Want horn?
ㅤㅤㅤㅤㅤYes
ㅤㅤㅤㅤㅤ|_________Download horn remover for Neverwinter (Dependency for horn)
ㅤㅤㅤㅤㅤ|_________Download a horn of your choice
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ |_____Horns
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn A
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn B
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn C

MAIN: Calimshan head
|_____Want horn?
ㅤㅤㅤㅤㅤYes
ㅤㅤㅤㅤㅤ|_________Download horn remover for Calimshan (Dependency for horn)
ㅤㅤㅤㅤㅤ|_________Download a horn of your choice
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ |_____Horns
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn A
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn B
ㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤㅤ Horn C

You don't HAVE to cater for this. Just letting you know something like this can exist.

Dependencies are already handled at the package level, not mod level. Each mod is made up of packages, one is the main package and rest are optional.

[Oyster Sauce]

Need to adjust this to make it more obvious which file is the main download and which are optional files, adjust the UI a bit.

soulless logo...

[rusty_shackleford]

Probably going to do the bare minimum just to get it out the door for a release rather than trying to get all the features in prior to release tho. Lots of stuff I've been working on is just niceties that can be added post launch.

[rusty_shackleford]

Going to just make viewing a user's mods redirect to the search page instead, no reason to duplicate functionality.

Selection_024.webp

The last mod is there because the user is a maintainer, but not the primary author. Not sure if searches for author should only be for the primary owner

[rusty_shackleford]

Need to adjust this to make it more obvious which file is the main download and which are optional files, adjust the UI a bit.

soulless logo...

Selection_025.webp

[Magick]

Going to just make viewing a user's mods redirect to the search page instead, no reason to duplicate functionality.


The last mod is there because the user is a maintainer, but not the primary author. Not sure if searches for author should only be for the primary owner

I think default search being both author / maintainer is fine.

But as always Rusty, best of both! Add a "authored only" checkbox or something.

[Vergil]

what mods has bobt made btw

[Magick]

what mods has bobt made btw

Nothing public.

[Vergil]

what mods has bobt made btw

Nothing

ok

[Stack of Turtles]

what mods has bobt made btw

he made all the mods his wife put her name on, obviously

[Vergil]

what mods has bobt made btw

he made all the mods his wife put her name on, obviously

*Our wife

[Nooneatall]

what mods has bobt made btw

Nothing public.

A lot of weird @Red7 style porn mods?

[Havitner]

How would one upload a mod that features multiple variations of a single core file?
-Multiple folders in one downloaded archive?
-Pick one to be the main file and note that the others are non-dependent replacements?
-Have multiple core file entries?

[rusty_shackleford]

How would one upload a mod that features multiple variations of a single core file?
-Multiple folders in one downloaded archive?
-Pick one to be the main file and note that the others are non-dependent replacements?
-Have multiple core file entries?

Multiple main packages, I'd assume.
Or a single main package containing common files + optionals.

[rusty_shackleford]

Selection_020.webp

Process is:
Submit a new mod -> edit mod(therefore eliminates any duplication between submission/editing, add packages, media, changelog, etc.,) -> request approval if the mod has not been approved, all mods require manual approval the first time they're listed

[rusty_shackleford]

Process is:
Submit a new mod -> edit mod(therefore eliminates any duplication between submission/editing, add packages, media, changelog, etc.,) -> request approval if the mod has not been approved, all mods require manual approval the first time they're listed

You'll be taken to your mod page after creating it, which you can then edit.

Selection_021.webp

I hope this is making sense.

(Yes, I know the endorse/edit buttons need to be tweaked)

[Vergil]

Will the comments section be it's own thing or is it still connected to a thread on the forum?
Does uploading a mod still make a forum thread?

[rusty_shackleford]

Will the comments section be it's own thing or is it still connected to a thread on the forum?

I don't know yet. Maybe.

Does uploading a mod still make a forum thread?

No.

[Vergil]

Comments being it's own thing and not a thread would be nice

[rusty_shackleford]

Comments being it's own thing and not a thread would be nice

It probably will be. But I also don't know if it will be available in the first release, as I'm cutting out non-essential features.
So, first release might be people just linking to a discussion thread on the forums. Then an actual comment system builtin later.

[Havitner]

all mods require manual approval the first time they're listed

Enjoy manually approving my 'fixes a five pixel color mismatch in the GUI of a submenu in a particular gamecube game [dolphin EMU only]' mods.

[rusty_shackleford]

all mods require manual approval the first time they're listed

Enjoy manually approving my 'fixes a five pixel color mismatch in the GUI of a submenu in a particular gamecube game [dolphin EMU only]' mods.

Are you volunteering to be our first modhq janny?

[orinEsque]

Looks good!

[Vergil]

Manual approval is kinda stupid tbh and will make people not wanna bother

[loregamer]

I think some users should be verified and not require manual approval for every mod, but there needs to be safeguards against brigarding and require approval for the masses

[rusty_shackleford]

Manual approval is kinda stupid tbh and will make people not wanna bother

opinions?

[orinEsque]

Manual approval is kinda stupid tbh and will make people not wanna bother

opinions?

Hmm I'm considering various scenarios here. I'm not sure there's a right answer:

For
- You can keep spam and porn/faggotry/illegal stuff without users having to see it.
- Where you aren't getting tons of submissions a day this is easy to do
- Nexus ****** force this on first time users to prevent bots / for virus scanning anyway

Against
- The wait may put people off from posting
- If your site gets popular this won't be sustainable even with a staff of 20 people
- You can simply rely on user reports to take down porn/spam

My personal opinion is: require approval for first/first 3 mod submission. And obviously white list people who are known modders.

[loregamer]

Manual approval is kinda stupid tbh and will make people not wanna bother

opinions?

I think you can just do approvals the same way the forum handles first time posters