cause the are almost guaranteed to not be bug free
and sometimes it isn't even a bug
example
in the last moth of 0.5 someone made a change in the git/autobuild which led to the server being unplayable to all 0.5 users...
also if a official map is updated in autobuild then the release users will experience odd bugs (like g-23 doors broken) (invisable obsticals on solarium)
also ... it is safe to use A autobuild when you know it is safe
just DONT set it to update with each new autobuild ... cuase then you are in dangerous waters
04-28-2012, 07:03 PM (This post was last modified: 04-28-2012, 07:10 PM by W4RP1G.)
(04-28-2012, 06:39 PM)hutty Wrote: isn't amo amounts a config setting?
also ... it is safe to use A autobuild when you know it is safe
just DONT set it to update with each new autobuild ... cuase then you are in dangerous waters
Well, I haven't messed with the minsta ammo drop much, but it's default is set to 5, yet it drops somewhere around 30 ammo(I think). There was a thread about it a few weeks ago where it was determined that it was a bug that was fixed in an update.
So I can use the autobuild to update to a specific build? I thought it automatically put you at the latest version? And can recommend a recent build that is stable?
Edit: Or better yet, there perhaps an updated r-sync-data.pk3 I can download that resolves this issue?
as said, auto-builds are experimental. however, if you update your auto-build server fairly often, those temp bugs that may be in there should be gone fairly quick. the larger problem is possibly incompatible clients due to experimental/new code and/or data.
If you want a "cutting edge" server, your better off using the GIT version as it just fetch the changes and not the whole damn game each update
that said, if you have a 'non release' server or really different settings, plz make sure the hostname and motd tells that.
(04-29-2012, 04:44 PM)tZork Wrote: If you want a "cutting edge" server, your better off using the GIT version as it just fetch the changes and not the whole damn game each update
It's rsync-based, so it's not checking the whole thing in every time you update :>
04-30-2012, 03:17 AM (This post was last modified: 04-30-2012, 05:32 AM by rafallus.)
BTW. can you make an exclusion list for files to check for rsync-updater? Like if you modified some stuff (swapped the music in my case), to not have it redownloaded every time you update?
04-30-2012, 01:09 PM (This post was last modified: 04-30-2012, 01:13 PM by Mr. Bougo.)
If you want to swap music, do that in your personal data directory. That won't be touched by the updater. In general, it is strongly advised that you do not touch the install directory.
EDIT: To clarify some more: read about pk3's. You want to have the music file under the same path as the original, but in your data directory. You can do this using a pk3dir or a pk3, or no pk3 at all and directly store it under the path you want to override, in your data directory.
For example, if you want to override music/foo.ogg, you have three options:
Create a zip archive called zzz_blablablamymusic.pk3 containing music/foo.ogg, put it in your personal data directory
Create a directory called zzz_blablablamymusic.pk3dir containing music/foo.ogg, put it in your personal directory
Put foo.ogg in your personal directory: ~/.xonotic/data/music/foo.ogg if you're on linux for example
(04-29-2012, 04:44 PM)tZork Wrote: If you want a "cutting edge" server, your better off using the GIT version as it just fetch the changes and not the whole damn game each update
It's rsync-based, so it's not checking the whole thing in every time you update :>
autobuild is not "based" on any push or pull tech, its simply a build - but i did forget there's a way to rsync it, so good catch. still, its likely more effective in the long run (and certainly more flexible) to use GIT if what one wants is a always updated server.
Quote:If you want to swap music, do that in your personal data directory. That won't be touched by the updater. In general, it is strongly advised that you do not touch the install directory.
EDIT: To clarify some more: read about pk3's. You want to have the music file under the same path as the original, but in your data directory. You can do this using a pk3dir or a pk3, or no pk3 at all and directly store it under the path you want to override, in your data directory.
For example, if you want to override music/foo.ogg, you have three options:
Create a zip archive called zzz_blablablamymusic.pk3 containing music/foo.ogg, put it in your personal data directory
Create a directory called zzz_blablablamymusic.pk3dir containing music/foo.ogg, put it in your personal directory
Put foo.ogg in your personal directory: ~/.xonotic/data/music/foo.ogg if you're on linux for example
Thanks. I've moved modified xonotic-rsync-music.pk3 into personal data, and so did with maps. Looks like they are recognized by game without replacing/deleting them with each update.
The question is: if I have this other xonotic-rsync-music.pk3 in personal data, is it possible to delete old xonotic-rsync-music.pk3 to save space and not having it redownload by rsync-updater? Because it doesn't seem to be the case when I try to update.
BTW. nice mortar rounds since autobuild. Got a nice laugh.
![[Image: 4XODR.png]](http://i.imgur.com/4XODR.png)
