[bug?]Updater reverting files

[willy_sunny]

As we've all like to modify settings here and there

however, when updating, everything will be reverted.

== list of items that were reverted due to updater ==

1. Anything with "default" in it (like default sound pack, default skin, etc)
2. Apps.ini
3. Styles
4. Custom Lua Script

And especially point 4, this is actually becoming annoying = =

it's custom.lua, it's supposed for users to add in custom scripts

However, whenever it was updated, the custom.lua will also be overwritten

AND NO WARNING WAS ISSUED

So bye bye my beautiful lua scripts, all gone poof now >.<

[SilentStorm]

Open up File Properties of custom.lua and restore an Earlier Version from the same named Tab.

[Screech]

SilentStorm, not an option with XP.

I agree, there are some files that should not be over written with every build. custom.lua is near the top of that list. For that apps.ini if there is a way to include a new userapps.ini file and not update the include file every update that would work best to allow for the devs to update their apps.ini without removed user added apps.

I think the default skin and sound files work as they should though. If you want to edit the defaults, first copy to a new folder for customizing.

[Alcazar]

Why not making backups of files before updating?
We would lose some files too (scripts and sounds) whend updating blindly.
For custom.lua, just copy your scripts to a temp file and insert them back into the new custom.lua.

[SilentStorm]

SilentStorm, not an option with XP.

XP is dead. Period.

Not my fault if people keep using antique, decades old, unsupported Operating Systems.

[Screech]

XP is dead. Period.

Not my fault if people keep using antique, decades old, unsupported Operating Systems.

LOL, its not even 1 decade yet, close but yet. And with the crap OS Vista in the middle its no wander most people stayed with XP. I still run XP on 2 PCs here that its not worth the cost of upgrading on for there use and hardware specs. And I have my XP mode that came with my nice shiny new Windows 7 install that I also use for testing.

XP may be long in the tooth, but it ain't dead.

But on topic, using the OS file version tracker is just a work around that should be addressed at the source of the problem. In this case TS3's update logic. As you may recall they had this same problem with the server's query whitelist file, after it was pointed out they changed that so it doesn't overwrite an existing file.

Another reason using OS level version tracker may not work is having it disabled. I disable all of my indexing and version tracking settings on my laptop with the SSD installed.


And. If you read the system requirements it list Windows 2000 and XP, so for that fact alone support of that needs to be considered.

[willy_sunny]

XP is dead. Period.

Not my fault if people keep using antique, decades old, unsupported Operating Systems.

Just to fight the statement, this happens with both linux + mac as well.

Can't say that's antique now, could you?

Why not making backups of files before updating?
We would lose some files too (scripts and sounds) whend updating blindly.
For custom.lua, just copy your scripts to a temp file and insert them back into the new custom.lua.

This is the problem, most people tend to FORGOT about it.

Just a warning at least should be enough to let users to be aware of the process, this is what I'm saying.

[dante696]

Quick: This wan't be changed and you won't get a warning
Long:
1. This is all default and should not be changed by others
2. Make a backup of your own custom ini
3. Styles won't be touched us and the developers just grab, what they get from QT.

This will be changed:
4. With client beta 23 Custom Lua Scripts won't get overwritten with our updater.