Author Topic: Compile to .dso?  (Read 1314 times)

How can you compile a .cs to a .dso file using Blockland?
I used my SDK demo to create a .dso but this comes up

ERROR: DSO file "Add-Ons/Weapon_script/weapon_script.cs.dso" is version 36, expected version 120

You'd probably need the same engine version as Blockland to properly compile it to .dso, also if you're going to release something complied as a dso that's breaking the rules.

1. Badspot has a modified version of DSO format I believe.
2. RTB and Badspot will most likely fail any add-ons that contain DSO files.

There's a function in the current version of Blockland to compile it. However I suggest NOT doing that unless you keep the mod private.

There is no reason for needing to encrypt add-ons.

Tom

Unless you want to hide something...
Why I would assume any DSO file add-on has something bad hidden.

What do you need to hide?

There's a function in the current version of Blockland to compile it. However I suggest NOT doing that unless you keep the mod private.
And may I ask, what is that function?

I wont be the one to say.

There is no existing way to compile and output a dso file using Blockland. Nor is there a way to use any other program to create a dso for Blockland. Even if you magically figured out how, you would not be allowed to release the add-on.

And most importantly, there is no valid reason to need to dso an add-on.
« Last Edit: July 16, 2009, 02:40:42 AM by Ephialtes »

There is no existing way to compile and output a dso file using Blockland. Nor is there a way to use any other program to create a dso for Blockland. Even if you magically figured out how, you would not be allowed to release the add-on.

And most importantly, there is no valid reason to need to dso an add-on.
OMG TBM ALL OVER AGAIN D:



And most importantly, there is no valid reason to need to dso an add-on.

What if you just dont want anyone to use it as a resource?

Don't release it then. When you make things publicly available you have to accept that people can do whatever the hell they want with it. I doubt whatever you've made is something so revolutionary that nobody else could replicate it.

Releasing a mod that no one else can mod, is just hypocrisy.