Missing Cob Business
Moderator: Moderators
Missing Cob Business
You might want to look at your code again, and make sure it lookings for a cob file with the same name as the fbi file, and not the same name as the .3do file.
I'm going to speak in OTA terms here, as I'm not quite as familiar with the inner workings of Spring as I am with OTA: The thing is, the filename of the .FBI file is completely arbitrary and irrelevent. The thing that matters is the "UnitName=xxx;" tag in the FBI file. This is the unit's true internal name. This is the name the model and script must have, period. This is also the name referenced in download TDF files and other places in OTA. It just so happens that almost every unit shares the UnitName = FBI filename convention because Cavedog started it, and it works for organizational means. It just makes sense. If you really wanted, you could probably have multiple units defined in one .FBI file (in OTA, at least) without any detrimental results technically.
The point of this is that every unit that worked in OTA will have names that are exactly the same for the UnitName tag, the 3do filename, and the cob filename. Therefore, it is not unreasonable at all for Spring to skip loading the UnitName tag from the FBI and just compare filenames, since if the unit worked in the first place (in regards to file names) in OTA, it will work in Spring. That is unless it has spaces in the name, which as stated, Spring doesn't like. Of course, Spring may very well load the UnitName tag from the FBI for the basis of comparison. I haven't really poked in that part of the source that much.
I'm not trying to say your point is totally invalid--there may be some very obscure scenario that I can't think of which would cause this, but going by what I already know I'd have to come to the conclusion that the problem lies somewhere else, not in the naming convention, unless the naming convention contains spaces.
The point of this is that every unit that worked in OTA will have names that are exactly the same for the UnitName tag, the 3do filename, and the cob filename. Therefore, it is not unreasonable at all for Spring to skip loading the UnitName tag from the FBI and just compare filenames, since if the unit worked in the first place (in regards to file names) in OTA, it will work in Spring. That is unless it has spaces in the name, which as stated, Spring doesn't like. Of course, Spring may very well load the UnitName tag from the FBI for the basis of comparison. I haven't really poked in that part of the source that much.
I'm not trying to say your point is totally invalid--there may be some very obscure scenario that I can't think of which would cause this, but going by what I already know I'd have to come to the conclusion that the problem lies somewhere else, not in the naming convention, unless the naming convention contains spaces.
You're wrong, Gnome.Gnome wrote:I'm going to speak in OTA terms here, as I'm not quite as familiar with the inner workings of Spring as I am with OTA: The thing is, the filename of the .FBI file is completely arbitrary and irrelevent. The thing that matters is the "UnitName=xxx;" tag in the FBI file. This is the unit's true internal name. This is the name the model and script must have, period. This is also the name referenced in download TDF files and other places in OTA. It just so happens that almost every unit shares the UnitName = FBI filename convention because Cavedog started it, and it works for organizational means. It just makes sense. If you really wanted, you could probably have multiple units defined in one .FBI file (in OTA, at least) without any detrimental results technically.
The point of this is that every unit that worked in OTA will have names that are exactly the same for the UnitName tag, the 3do filename, and the cob filename. Therefore, it is not unreasonable at all for Spring to skip loading the UnitName tag from the FBI and just compare filenames, since if the unit worked in the first place (in regards to file names) in OTA, it will work in Spring. That is unless it has spaces in the name, which as stated, Spring doesn't like. Of course, Spring may very well load the UnitName tag from the FBI for the basis of comparison. I haven't really poked in that part of the source that much.
I'm not trying to say your point is totally invalid--there may be some very obscure scenario that I can't think of which would cause this, but going by what I already know I'd have to come to the conclusion that the problem lies somewhere else, not in the naming convention, unless the naming convention contains spaces.
The .fbi MUST have the same name as the UnitName=xxx; for TA or the unit won't work. Script must also be the same. 3do is defined in the fbi and so can be anything. So neuralize has a very valid point.
Really? I never had any problems with different names... or maybe my memory is just shaky :D Oh well, when you're wrong you're wrong... *shrug*FLOZi wrote:You're wrong, Gnome.
The .fbi MUST have the same name as the UnitName=xxx; for TA or the unit won't work. Script must also be the same. 3do is defined in the fbi and so can be anything. So neuralize has a very valid point.
