Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

By the way, does anyone have a list of the confirmed outstanding bugs? It can't be that large.

Beginner Joined: 09 Oct 2012 Posts: 18

Beginner Joined: 25 Oct 2012 Posts: 11

Came here to suggest open source release if the project is truly dead... I wouldn't go as far as saying "it's the right thing to do" but it is certainly the best way of keeping the software alive and well and working into the future. If thousands of hours went into making it what it is today, it would be a shame to just let it rot and fall into disrepair rather than letting folks continue the evolution of the software.

Amorelia- I think it'd be ideal to have a Wiki for it so that the community can keep the documentation up-to-date and provide script snippets, etc. But I agree with you on the documentation front.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Don't need a Wiki, we already have the online helpfiles stashed in the CMud Support section of this website. Everyone has access to them, which means regular players can leave comments if they find something wrong, a workaround for something buggy, or a better explanation of stuff that seemed unclear. If/when the comments get too long, Gurus can incorporate them into the main helpfile so that the proper information is kept visible/at the top.

Newbie Joined: 21 Aug 2010 Posts: 1

Just a random suggestion as far as the money issue. One of the things I truely hate the most, is making triggers, updating a map, etc. on one computer and then having to export the settings, and re-import on say my laptop. A lot of times I forget that I even made changes and eventually I end up over writing something on one or the other.

As a possible (not to difficult I would think) solution to help bring in some consistent money - why not make cmud/zmud registered to the same user automatically send the exported code to ya'll, and on the start of cmud check to make sure the latest version is installed. I'd pay a small fee per month recurring if this was possible. If people want to upgrade their subscription, they can pay the monthly fee. If they don't want to and are better at keeping their versions updated manually than I am, power to them they can pay the one time fee to subscribe.

Since you already have the application registering to a specific user, it seems like with a little bit of hard drive space and some minimal bandwidth you could bring in some recurring income and hopefully continue development in other aspects?

Sorcerer Joined: 15 Apr 2011 Posts: 809

This was planned years ago, but at this point I think it's unlikely that it'll ever happen. Have you tried using dropbox to keep your settings synced across multiple computers?

Posted: Fri Nov 16, 2012 3:38 am

Just wanted to say as a loyal customer (I even bought zmapper Laughing

) thanks for all the work you've done. I'm sad it will bitrot but what can you do? For those asking for 'open sourcing' it's pretty much never going to be feasible due to the amount of commercial libraries it uses. Even if Zugg wanted to open-source it, which is noone's business but his own, it won't be in a compilable state and generally useless on its own.

So long Zugg, thanks for all the fish.

Newbie Joined: 04 Aug 2008 Posts: 9 Location: Washington

Took a while to learn this. Can we get an official announcement and sticky? Also Zugg, if you're not going to continue development. Make it an open source project. Let other's in. You're not making money anyway right? You can set up for donations to continue the project. The legacy will continue, the community will be happy, and it won't consume your time and financial resources. Think about it.

Sorcerer Joined: 15 Apr 2011 Posts: 809

About open source, see the post directly above yours. I agree a sticky would be nice though.

Newbie Joined: 16 Jan 2017 Posts: 1 Location: Earth

Since you've been gone -- is that a song? Things like patreon have cropped up.

I think you should set up a patreon account and when someone commits to a monthly donation level, you give the a special code that works for them only, since the mud client requires the internet, you can have it check with a server to see if the code is being used on just one computer (like the way mojang does account authentication), if account authentication fails the client is returned to a crippled state.

In that way if the donator stops their monthly donations you can deactivate their authentication.