Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: FUBAR-BDHR on January 08, 2009, 06:20:11 pm
-
Which ones effect validation and what determines if the tables are valid or not?
The main question is should simply adding a sun or planet or whatever using a stars .tbm break validation. It seem to.
-
Only things that could change behavior get validated. So, the list is basically: ships/armor/types, weapons, ai_profiles, scripting, species.
I don't see any reason that a stars tbm would mess anything up, unless it was a modified mission using said changes that was the actual cause of the validation problem.
-
Vid had a problem with validation in TBP due to hacked tables. Well we all get the hacked tables message but it still saves (in 3.6.10 at least). The only thing I believe he has that isn't stock TBP tables is a stars.tbm I made for him. I'll have him double check and check it myself to see what happens. Stats are saving for me on this machine so if I copy that .tbm over and it quits then it's most likely the cause.
Actually if it's a nebula mission a stars table entry could possible be used to cheat. Easy way around that is to not make nebula missions valid for squadwar.
-
Check multi.log too, it will list every tbl/tbm that it tries to validate as well as whether it was valid or not. The stars tbm should not show up in the list. If it does then let me know.
-
I just tried a quick test and it didn't show up in my multi.log. Hopefully Vid still has his from yesterdays session.
-
Vid found another file that was causing the problem. So looks like it is working just fine.