VITAS changed the topic of #spacedock to: Problems?: https://github.com/KSP-SpaceDock/SpaceDock/issues | Matrix/Riot Chat: https://im.52k.de +spacedock:52k.de Feel free to ask for help, we only bite a little bit! | If you want to help, please check https://github.com/KSP-SpaceDock/SpaceDock-Backend/issues/5 :) | <VITAS> inet users have the attentionspan of a squirrel...
KineticSloth8StoneBlue[m has joined #spacedock
<KineticSloth8StoneBlue[m> So, just wondering, is it too outlandish, to suggest mebbe adding an optional additional version field to each release, for a minimum version of KSP that a mod is known to work for, and officially still supported by the dev?
<KineticSloth8StoneBlue[m> ie below... v1.8.1 to 1.10.0 is only implied for the last release...
<KineticSloth8StoneBlue[m> and in this case, the dev *did* include in the details which version of KSP it was origianlly released for... many devs do NOT do that, and it can leave people guessing, and hence posting, and possibly pestering devs in the release thread, if a release is backward compatable w/ previous KSP versions... vOv
<KineticSloth8StoneBlue[m> and would there be any cons to doing it?
<KineticSloth8StoneBlue[m> And would it be too difficult to implement?
* KineticSloth8StoneBlue[m uploaded an image: 20-09-03_at_08.56_AM.PNG (100KB) < https://matrix.52k.de/_matrix/media/r0/download/52k.de/KXXVjVteeVcNLKqRHBfkFTFo >
VITAS[m] has joined #spacedock
<VITAS[m]> so you want a range of versions a mod works with?
<VITAS[m]> I think a range opens the question of: who can add min max compatible versions (e.g. for mods that arent in active dev anymore)
<KineticSloth8StoneBlue[m> well, I think limiting it to being entered/updated only by the authorized users on the mod would be fine.
<KineticSloth8StoneBlue[m> I wouldnt expect just anyone to be able to go back in an update it for inactive/old mods
<KineticSloth8StoneBlue[m> and mebbe lock it on previous releases, once a new release is added... vOv
<KineticSloth8StoneBlue[m> so it can only be edited on the last/latest release
<KineticSloth8StoneBlue[m> also, if it could only be edited on the last/latest release, it might be less headache to implement it as a new feature?
<KineticSloth8StoneBlue[m> just on releases now and going forward?
mastops12[m] has joined #spacedock
<mastops12[m]> hi i have a question how do i install true haze
<KineticSloth8StoneBlue[m> wot is "true haze"? a mod?
* mastops12[m] uploaded an image: unknown.png (2KB) < https://matrix.52k.de/_matrix/media/r0/download/52k.de/hjPuyOmidEvHfyhHVUjmyIEh >
<mastops12[m]> mod
<VITAS[m]> lets ask DasSkelett when hes back from his expedition
<VITAS[m]> if he wants to implement such a thing
<VITAS[m]> i think its a nice feature
* mastops12[m] uploaded an image: ABGmSlJ.png (502KB) < https://matrix.52k.de/_matrix/media/r0/download/52k.de/PdBlebeCWHgOQewVHjQyZAsv >
<mastops12[m]> I saw this in a forum about the mod
<mastops12[m]> is it possible to place that atmosphere effect in another game as the picture shows?
<mastops12[m]> xd
<VITAS[m]> uhm you might want to ask on the ksp forums
<VITAS[m]> roblox isnt ksp
<mastops12[m]> https://forum.kerbalspaceprogram.com/index.php?/topic/103963-wip110x-scatterer-atmospheric-scattering-v00632-26082020/page/203/
<mastops12[m]> the image redirects me to this forum idk
<VITAS[m]> this is no forum
<VITAS[m]> this is a chat
<VITAS[m]> its best to ask the devs on the ksp forum thread itself
<VITAS[m]> they are also the ones who can give you perimssions to use parts of their mods out of context if need be
<KineticSloth8StoneBlue[m> Not to discourage mod discussion here, but your question is *VERY* involved to answer, spanning the working os not just KSP, but TWO games... so you would be better served asking elsewhere...
<KineticSloth8StoneBlue[m> mebbe beginning with the KSP forums you linked...
mastops12[m] has quit [Quit: Idle timeout reached: 10800s]
VITAS[m] has quit [Quit: Idle timeout reached: 10800s]
KineticSloth8StoneBlue[m has quit [Quit: Idle timeout reached: 10800s]