View Issue Details

IDProjectCategoryView StatusLast Update
0001113FSSCPmultiplayerpublic2006-11-01 04:20
Reporterkarajorma Assigned Totaylor  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
PlatformWindowsOSWindows XP HomeOS VersionSP2
Summary0001113: Multidata option not working properly
DescriptionIf you use the transfer missions to multidata option (Which you absolutely should if you're developing multiplayer missions) it doesn't actually protect you.

The idea behind multidata appears to be that if someone hosts an old version of your mission it xfers to multidata rather than on top of your newer version.

Unfortunately at the moment the game first deletes your copy of the mission from the missions folder, xfers the different version from the host to multidata and then crashes complaining that it can't find the mission because there's nothing in the missions folder.
Steps To ReproduceHave two identical copies of a mission on two computers mission folders. Alter one of them.

Host the game on that machine.

Select the transfer to multidata option from multiplayer options screen on the other computer.
TagsNo tags attached.

Activities

taylor

2006-10-15 18:07

administrator   ~0006896

Retail did this too. The problem is that missions in data/missions/ will be loaded before ones in data/multidata/ through cfopen(). So if a mission with the same filename exists in the missions directory it will override the one in multidata. That's why it deletes both copies if they exist.

There isn't a simple or clean way to fix this, since pretty much every fix I can think of comes with multiple consequences which are easily worse.

The best way to deal with this is just change how you do it. It will only delete a normal file, and it will only look in root(0). This means that if you use a mod directory, just don't keep the mission in your primary mod directory and it won't get deleted. Or, keep it in a VP and it can't be deleted then either.

taylor

2006-10-18 23:11

administrator   ~0006905

Not-A-Bug


Closered.

Issue History

Date Modified Username Field Change
2006-10-15 15:50 karajorma New Issue
2006-10-15 18:07 taylor Note Added: 0006896
2006-10-18 23:11 taylor Status assigned => closed
2006-10-18 23:11 taylor Note Added: 0006905
2006-11-01 04:20 taylor Resolution open => no change required