Page 2 of 2

Re: PixelPerfection V3.6 - By XSSheep -Converted by mcrescon

PostPosted: Thu Dec 13, 2018 20:05
by sofar
texmex wrote:Just wanted to pop in and tell about my work on PP support for Minetest Game and several mods. I've superseded what mcresconvert can do by converting and editing manually both XSSheep's original textures and by collecting textures from PP "support packs". It's for 5.0.0 and lives over here. I may create another thread for it though that's also a bit weird.


Thanks for doing this. We'll change links and copies on contentdb with these updates. I've adjusted the main topic text already, so people know they can get enhancements to the texture pack from there.

Re: PixelPerfection - By XSSheep

PostPosted: Fri Dec 14, 2018 18:59
by sofar
Contendb now has a new release as well, pointing to the latest version in github,

Re: PixelPerfection - By XSSheep

PostPosted: Wed Dec 26, 2018 09:11
by texmex
Thanks! PP is about to get a full revisioning by author btw. Even more perfection!

Image

Re: PixelPerfection - By XSSheep

PostPosted: Sun Mar 03, 2019 16:21
by BlazeGamingUnltd
wow, just WOW!

Re: PixelPerfection - By XSSheep

PostPosted: Tue Mar 05, 2019 14:00
by texmex
sofar: Please create a new ContentDB release from master branch with a 5.0.0 client minimum requirement.

Re: PixelPerfection - By XSSheep

PostPosted: Tue Mar 05, 2019 19:49
by sofar
Done. We should make tags from now on, though, for contentdb.

Re: PixelPerfection - By XSSheep

PostPosted: Wed Mar 06, 2019 13:23
by texmex
Okay, how do they work?

Re: PixelPerfection - By XSSheep

PostPosted: Wed Mar 06, 2019 18:34
by sofar
You can make tags through the github web interface. It's just an easy way of saying "this isn't just a git commit, I really like this commit for a reason and am going to give it a special name".

git checkout $yourcommit
git tag v5.0.0-1
git push --tags

Re: PixelPerfection - By XSSheep

PostPosted: Thu Mar 07, 2019 16:06
by texmex
Cool, but how are tags treated in contentdb? Why is it better than just an ordinary release from master?

Re: PixelPerfection - By XSSheep

PostPosted: Fri Mar 08, 2019 06:38
by sofar
texmex wrote:Cool, but how are tags treated in contentdb? Why is it better than just an ordinary release from master?


Tags can only be created in github, not in CDB. Tags are better because
Code: Select all
e234f8793a51
really doesn't mean anything to a normal human being :)

Re: PixelPerfection - By XSSheep

PostPosted: Fri Mar 08, 2019 06:54
by texmex
But in the context of a TP, does 1.1.3 really mean that much more?

Re: PixelPerfection - By XSSheep

PostPosted: Fri Mar 08, 2019 21:47
by sofar
texmex wrote:But in the context of a TP, does 1.1.3 really mean that much more?


It won't if you have that perception. It will if you don't have that perception.

By and large it helps people to understand what the maturity of your software is if you assign logical and understandable version numbers to "certain versions" of your project. This isn't something new: 0.4.17.1 sounds less stable than 5.0.0. However, note that version numbers are for the consumer, and not for the project creator. If you are exclusively a creator, you are most likely biased and not likely to see value in version numbers and tags since you already know your way around the code. So if you don't "get it" now, that's fine, just start tagging your projects and don't try to understand it :).

Re: PixelPerfection - By XSSheep

PostPosted: Fri Mar 08, 2019 22:13
by texmex
I do understand the point for regular software but TPs are a little different. It’s only ”1.0” when full texture coverage (of whatever target game, traditionally MTG) has been completed. If it’s not constantly maintained to cover new target game textures, it will become less mature and thus doesn’t really deserve to be called 1.0 any more. The fact that it once was complete should be interesting to no one.

That’s my thinking anyway. There could be a tagging convention that just follows the target game version, like 4.17.1 or 5.0.0.