[Beta Branch Patchnotes 0.10.3.7509]

how in the hell did you even understand that ?

[Beta Branch Patchnotes 0.10.3.7509]

this is why you make scale step .05 then make the the width and height needed, and just stack them on top of each other lol problem solved, though it is quite blinding at times :D

 

also what is the time frame that we may see the beta branch going to live? cant wait for the repair window additions and well just about all the other things

[[Mod] Captined ship salvage command]

so this script needs to be on the server as well as the client for it to work ? cause if so that would explain why nothing is working now, lol the ship will not even escort me now just sits there.

 

yea im almost positive it does at this point, well i found a bug, if the script is not on the server you are playing on and you tell it to salvage or clean sector it will do nothing, .... ever lol any commands after that are ignored, unless you disconnect and wait then reconnect.

[working on a a mod manager]

We need something like a Addons -/ Mods folder to put scripts in.

 

Like you have a init.lua, wich runs the server automatic. You can then easy add player scripts, and things like that.

 

When im not wrong, this should already been possible. Make yourself a script with a file.find system.

Like:

 

data/mods/

 

Mods folder includes:

 

server(folder)
sector(folder)
galaxy(folder)
player(folder)

player.lua ( gets auto added via init.lua, this file manages the player files )
init.lua  -initializes as server
....

 

then you need to edit the raw server.lua and include your modular system wich finds all the files in your custom folder and adds them.

This method is just like the original one, but its easier to install & updates of avorion can be applied easyly.

 

 

This is just some kind of thought of me.

 

this is not a bad idea, i could do this with the mod manager to force something like this, however it would be broken on every update most likely, of course depending on how updates are done, but either way, this is all for not if the dev's decide to go with the steam workshop. also the mod manager would only be for client side mods.

 

i have sent the dev a msg about all this and just waiting to hear back.

[working on a a mod manager]

awesome, and this will mature and get better with time as well, i am also working on a file monitor as well, so basically when you install a script, the manager will remember the file that was updated/added, and if another mod is to change or replace that file it will give you a warning.

 

didnt think about this but are there plans on using steam's workshop for mods? cause if so then this is pretty much a useless endeavor lol

[Is first person possible?]

it is persistant unless you specify what block to center / mirror off of, there is a button in the build menu that allows you to set any block as the mirror block, so you can offset your mirroring, but what ever you select does stay consistent unless changed by you.

[working on a a mod manager]

so i have been working on a mod manager the last few days and i have come to the realization that there is really no way to know were the script should go aside from the developer of the script telling us.

 

so we as modders, and code monkeys need to come up with a way that will not affect the script to designate its location a standard if you will, also this will help future releases, other mod managers, other modders, and potential users of the mods to easily figure out were the mods belong.

 

so what i was thinking was lets get a list of ways we could accomplish this and put them all here.

 

Please read all options and try not to re-post ones that are already listed, also if you think something will not work, please explain in detail why it would not work and keep it civil.

 

_____________________________________________

I will kick this off.

 

simply add this to the beginning of your script.

 

-- ( Location/were/script/goes )

 

this way (atleast in my usage) i can search the script with regular expression and grab what is after -- and between ( )