Post: #1

Hi guys,
I would like to make a suggestion to sphere structure.

Every time that the server release a new update, I feel really happy and really sad. Sad because I know that in order to use it, I'll have to implement all my modification to every single file again. And that's really something that takes time.

I have been trying my best to make my system so I would reduce this kind of thing, but still, in the end I have allot of modifications to the sphere script itself that I cannot help but change it to the file.

So my suggestion is to sphere implement a reading file that reads after all the scripts, applying the changes in it to the current script pack.

So lets say, in the end you don't have to change any file, because all your scripts and modifications will be applied to the sphere by this last file.

So, modifications to sphere.ini information, and at all sphere scripts, will be over read by this file.

This is an Example:

So whenever sphere is updated I just have to drop the new pack on the folder and keep going with my server.

Is this possible? What do you guys think?

Thanks!

Post: #2

good idea, woulbe be really cool

Post: #3

This is why the revisions viewer was implemented (However its down now because of Ben's net problems), you can update via svn from there.

Also, I always had my modifications in a custom folder, even regionresource changes, or whatever. Just to be able to delete scripts (not my folder) and place the new ones without any problem.

Post: #4

It is working fine here
http://spherescripts.sytes.net/listing.p...cript+Pack