Added new Bliss GitHub

thevisad

Moderator
Staff member
Not sure what happened with the Bliss repo that ayan4m1 was admining it suddenly disappeared earlier today. Luckily I had just downloaded a copy of the updated source yesterday.

You can access the github here I merged all of the files back into the build that were on blissrepo back into the package. I created a new development branch as well.
 
No clue as of yet, I have not seen a posting anywhere about it and ayan4m1 has not responded to the email I sent him last night.
 
I use Bliss and as long as I host it and have others to assist I will keep the project as active as I can. I am a c/php language developer so it will take me a bit to get up to snuff on perl.
 
Hey,

thanks for uploading the recent version.

We've also used Bliss for 5+ months now and it would be a shame if Ayan would really stop working on it without any notice. Especially because I regard the DB scheme (also regarding the updates) and the setup process by far the best of all private hives..

Would love to hear from ayan himself what exactly lead to this and if there will be an "official" successor who continues to maintain the repo
 
Code:
<GitHub> [DayZ-Private] ayan4m1 pushed 2 new commits to master: http://git.io/JQOvCA
<GitHub> DayZ-Private/master 48b0967 ayan4m1: Added more notices about not opening GitHub issues spuriously to README.md
<GitHub> DayZ-Private/master afe3fc0 ayan4m1: suppress cPBO output during build.pl
<p-schneider> @ayan4m1 Issue 601 was not fixed by the 2 commits you added, but you just closed it - I helped Quentix fix it by manually editing the generated pbo file - The mission file still will be invalid if you run "perl build.pl --world tavi --with-killmsgs --with-tavi-com"
<ayan4m1> What?
<ayan4m1> I updated the messaging package
<ayan4m1> What more was problematic?
<p-schneider> run perl build.pl --world tavi --with-killmsgs --with-tavi-com take a look at the mission file
<p-schneider> https://github.com/ayan4m1/DayZ-Private/issues/601#issuecomment-12722700
<p-schneider> the messaging package was just an additional think i found when i was looking for the issue quentix had
<ayan4m1> So sick of these worlds
<ayan4m1> These guys don't test shit
<ayan4m1> I didn't have time to
* ayan4m1 ([email protected]) has left #bliss (Done)
Then he closed the github and dayzprivate.com and blissrepo.com are 403.
 
Query - Since it looks like ayam4m1 is done with the admining of the bliss repo, I am mor ethen happy to continue this development. As such, should I leave the bliss github as pure bliss or include my inventory manager as part of the package?
 
I'm waiting to see what p-schneider wants to do first, he has done a lot to further bliss development since his fork.
 
I hope whoever takes up further development of Bliss leaves it as is, just the standard Chernarus private server with a few optional packages.
Any other programs/maps should just be considered addons/mods, and not packaged with the server itself.
 
It's sad to see him go, but I think he will be back. Just let things cool down and everything will hopefully be ok.
 
Found out about this today when i needed the dayz_server pbo lol, dayzprivate.com was forbidden (403), and IRC you had to be Voice+ to talk...
Anyways, thanks for re adding
 
Agreed with Pwnoz0r's thoughts, and Kanlaki. On that topic, anyone have the code that supported the blissrepo site?
 
It's sad to see him go, but I think he will be back. Just let things cool down and everything will hopefully be ok.

I would hope so as well; however, it is this sort of childish behavior that destroys trust in developers, lack of innovation through software sharing, code getting lost and users going WTF!? Regardless if he comes back or not, people will still be asking themselves "Will he do this again?" and "I better get all the code I can and keep it for myself in case he disappears again".

I know that I, for one, will never look at him again and think "reliable resource", I would assume others would feel the same. He may have his reasons, they may be legit, but they hurt the community in the long run unfortunately.
 
Back
Top