SROptionSet.dat structure?

Hi,

I'm here asking if someone has SROptionSet structure? or part of it? ... I'm pretty sure all settings like BLUR, TEXTURE, etc.. are saved into this file.

I'm actually interested on modify the "Window Mode" status, but starting with something will be good to move on quickly.

I dont think anyone worked on that but imo reversing the launcher is a viable option to get optionset structure

The Launcher only writes basic settings into silkcfg.dat which is consumed by sro_client and later saved into the real option set (SROptionSet).

Haven't looked that closely into the unknown fields.
- [Only registered and activated users can see links. Click Here To Register...]
- [Only registered and activated users can see links. Click Here To Register...]
- [Only registered and activated users can see links. Click Here To Register...]
- [Only registered and activated users can see links. Click Here To Register...]
- [Only registered and activated users can see links. Click Here To Register...]
- [Only registered and activated users can see links. Click Here To Register...]

Quote:

Originally Posted by DaxterSoul Haven't looked that closely into the unknown fields. - [Only registered and activated users can see links. Click Here To Register...] - [Only registered and activated users can see links. Click Here To Register...] - [Only registered and activated users can see links. Click Here To Register...] - [Only registered and activated users can see links. Click Here To Register...] - [Only registered and activated users can see links. Click Here To Register...] - [Only registered and activated users can see links. Click Here To Register...]

Wow, the whole structure is like gold for me.. thanks!

Quote:

Originally Posted by DaxterSoul The Launcher only writes basic settings into silkcfg.dat which is consumed by sro_client and later saved into the real option set (SROptionSet).

And you just answered part of my doubt about double settings..
So.. to get clear.. the window resolution from SROptionSet (as example), doesn't matter at the end because is always overwrited by the launcher settings on START?