RS is going to be history soon (max end of the year), and will be replaced by OSE which is much bigger in scope, has had hundreds of things fixed and is specifically being developed to be compatible with Oolite 1.73.4 and a future 1.74.
So if you want to help, I'd really love to have observant players such as you to test the OSE WiP version (V0.69 currently) and help with debugging that - OSE has a future, RS not.
RS is going to be history soon (max end of the year), and will be replaced by OSE which is much bigger in scope, has had hundreds of things fixed and is specifically being developed to be compatible with Oolite 1.73.4 and a future 1.74.
Yeah, I've seen this in some other threads too. RS has provided some nice things, so I'm really looking forward to OSE.
Lestradae wrote:
So if you want to help, I'd really love to have observant players such as you to test the OSE WiP version (V0.69 currently) and help with debugging that - OSE has a future, RS not.
I'll be happy to do so under one condition, that I can still carry on playing Oolite.
So, if 1.73.4 is in a ready-to-use state I'll go right ahead. Otherwise, if OSE also works with my current 1.73.3 then I'll go that way instead.
One of the benefits in cleaning up is in regards to signal/noise. By cleaning up much of the noise, it makes it vastly easier to spot the signals that we're looking for.
What I do want some advice about is gui_screen_string and d100_number, which get reportedfor the Trident Down OXP.
These methods are not allowed and are being removed. I would like to know the reason for this.
They should be allowed. And when you look closely, it only complains in two cases of its use, all other cases are accepted. I would think at an other reason. e.g used in a wrong context so the compiler does not recognise it.
I just tried myself but fail to see which line contain the problematic version.
EDIT; the last use of d100_number is wrong. It is used in the do part not in the condition part. So that whole line does not work. placing it a few lines lower inside the next condition list will fix the authors intentions.
EDIT; the last use of d100_number is wrong. It is used in the do part not in the condition part. So that whole line does not work. placing it a few lines lower inside the next condition list will fix the authors intentions.
<snip>
Same will be the case with the gui_screen_string error.
Excellent, thank you.
The gui_screen_string is from the do part in line 527. As the condition part already contains the same check, I have deleted line 527.
Now Oolite starts up with no logged errors, excluding RS of course.
Thanks Eric. I take it now that the authors of these mods should be contacted regarding these corrections.
The gui_screen_string is from the do part in line 527. As the condition part already contains the same check, I have deleted line 527.....
Thanks Eric. I take it now that the authors of these mods should be contacted regarding these corrections.
I just looked and found it also. to late
I think this pre processing of legacy scripts will find more bugs in future. It was not the objective but still, it is a nice addition for detecting errors in scripts.