The "I want something tested!" Circlejerk thread

I'd need to find a way for people to distribute their own copy of scripts/art/whatever via their own SVN repo. If I enable access for anybody to an repo, it'll break in no time. Letting everyone make their own repo on my server with a Empires copy in it will eat the server's disk space up very fast

 

make special folders for art and custom scripts? then just give some people a folder

 

I'm setting up an app like used on repo.or.cz

 

set it up with permisions for editing sub folders, and either set up users or what not, so for example, I'd only have access to the Metal_smith folder or files therein.

That or only give access to those who have proven themselves not a douche when it comes to taking things seriously. Rules would be don't touch anything but your own files.

You wouldn't even need to have the entire game in it, just the folder that contains the custom scripts with sub folders for the different people.

 

Umm, that's what I wanted to do.

 

In.

 

Why don't contributors without write access just make svn patches and distribute those? They work on everyones svn version and can be reverted. But oh wait, I guess thats more than 1 click, can't have that.

 

Drag's idea is far simpler. There's no reason people can't do it. SVN committing is overcomplicated.

 

Commiting is less difficult than creating a patch.

 

It has to be simple for the people you want to test it, not the people who want to create the updates.

"Just download this file and copy paste into such and such folder, but keep backups of "x" files just in case" sorta stuff is much more annoying than simply updating the folder and playing. Also you don't have to keep track of your scripts to make sure you are playing with the current version.

If someone feels it is too complicated to commit stuff to SVN, they probably won't have the drive to actually complete their projects anyhow.

 

You really think that it is too complicated to copy a folder then replace it?

If someone feels it is too complicated to perform a 5 second operation a computer, they probably wouldn't have the mental capacity to test a project anyhow.

 

Newb question: Whats the difference between a SVN patch and committing to the SVN?

Also, I'd be willing to help test.

 

Have you ever tried to work with people trying to test new scripts?

When you have to do all the DLing and making sure that it's the right version, then keep track yourself to make sure your files don't accidently get over written, it's a pain in the ass.

The rule of thumb is shit happens. The more you do to make sure shit can't happen, the better experience for everyone.

 

@ Scardybob.

It's just "upload folder" or SVN. Not SVN patch

 

a standardisation in distribution... so easy in concept, so hard in practise

 

How true. I guess most ppl will fail horribly with Git, so I just install GForge, it's easier to use.

 

GForge sucks, I'm searching for sth else.

 

Another silly question: Why aren't all scripts just part of the server build rather than also in the client build? It would seem to me to be easy to test multiple scripts if everyone got their values just from the server.

 

You can run a listen server on the client. Also, some script values are needed on the client.