Plugins for editor

[Mycekralid]

Will we have plugin-support for the editor so we could create special brushes and / or terrain-generators?

[Josh]

The original 3D World Studio had this functionality, and this is a likely feature in the future, using LuaJIT. This has a lot of advantageous:

• Plugins are easy to write and cross-platform compatible. (No compiling required.)
  
• Plugins can be precompiled as LuaJIT machine code and distributed to protect the source code.
  
• LuaJIT can compile C code into the Lua binary object! So it basically makes a cross-platform version of a DLL.
  

 

I'm a big fan of 3ds max's MaxScript plugins system, and would model the design after that.

[Mycekralid]

Cool You, Sir, are an awesome person

[Josh]

Here's some info on LuaJIT importing and compiling C code. It's rather amazing stuff:

http://luajit.org/ext_ffi.html

[Rick]

I understand they are trying to advertise that you don't have to make bindings but all the examples don't use custom user functions. Instead they are using functions that would come with the compiler. That's cool and all, but the ability to use 3rd party C code isn't really shown.

[ZioRed]

I agree with Rick, LUA may be nice (except myself) but it's really limiting if we could only use the engine functions and cannot rely on third party libraries to make everything possible (from creating a new window in the editor to customize the property panels when an object is selected in the scene etc). A full support to more advanced stuff would be more interesting, I honestly would better invest time in C++ support for editor plugins (our assets packages could contain editor plugins too to easily manage its gameplay scripts in the scene).

[Josh]

The idea is that if you want to offload the entire thing onto C++ you can just have Lua call a DLL function. So you can adjust the weighting between script and C++ as much as you like.

[YouGroove]

It depends on what type ot plugin you need, for simple stuff Lua is really enough without going C++. But again how many people plan to make C++ a plugins before asking some C++ version ?

[Mycekralid]

I'm not sure what YouGroove meant but if the possibility of calling dll functions is there, it seems fine to me

Would be nice if there would be a tutorial how to call these some day

For now normal commands on the engine would be fine as long as we could modify height maps livetime, like map generators or special brushes.

 

Thank you very much

[Josh]

Just throwing some ideas down. Something like this would be lot of fun:

function Plugin:Start()

local widget

 

--Identify what kind of plugin it is

self.type = Plugin.HeightmapGenerator

 

--Create info table

self.info={}

info.name="Josh's fractal noise generator"

info.author="Leadwerks Software"

info.company="Leadwerks Software"

info.url="www.leadwerks.com"

 

--Create UI table

self.ui={}

 

--Add a widget to the UI table

widget = {}

table.insert(self.ui,widget)

widget.type = Widget.Spinner

widget.name = "Noise"

widget.range = {1,100}

 

--Add another widget to the UI table

widget = {}

table.insert(self.ui,widget)

widget.type = Widget.Dropdown

widget.name = "Mode"

widget.options = {"Normal","Advanced","Extreme"}

 

end

 

function Plugin:Run(buffer,heightmap)

local noise = self.ui[1].value

local mode = self.ui[2].value

 

--Fractal stuff goes here--

 

end

[YouGroove]

Could it be some minimal plugin system to test or use for 3.1 , or too much work is going on for that ?

[Josh]

  On 12/6/2013 at 7:51 PM, YouGroove said:

Could it be some minimal plugin system to test or use for 3.1 , or too much work is going on for that ?

[Mycekralid]

  On 12/6/2013 at 7:51 PM, YouGroove said:

Could it be some minimal plugin system to test or use for 3.1 , or too much work is going on for that ?

  On 12/6/2013 at 7:52 PM, Josh said:

No, it won't be a minimal plugin system to test or use for 3.1 or no, it won't be too much work?

[YouGroove]

I mean : It is too much work to make some minimal plugin for the release of 3.1 ?

 

The response is just : NOPE , no plugin for 3.1 so let's wait for 3.2 roadmap.

[Mycekralid]

[nate066]

  On 12/7/2013 at 10:36 AM, YouGroove said:

I mean : It is too much work to make some minimal plugin for the release of 3.1 ?

 

The response is just : NOPE , no plugin for 3.1 so let's wait for 3.2 roadmap.

It would only take a month or 2 to have a prototype of a plugin system. Stop being so impatient. A plugin system will come when it ready. Just be happy for the OpenGL 4 support instead of complaining about what's not in leadwerks 3.1

[Guppy]

This still planned?

[Josh]

There's other stuff that will make a bigger impact with less effort, so this is not the highest priority right now. The stuff I think really matters is carving, CSG vertex manipulation, vegetation, decals, networking, roads, water, and vehicles. And water and vehicles will be done as of 3.4.

[YouGroove]

I agree it is not biggest priority. But it could be considered perhaps in the future ?

I need some sort of plugint to simply make regions types for the AI , and drop some AI Manager that controls all foes on some area level.

A plugin system would allow me to visually adjust the regions without needing the try,change values, try again etc ... method.

Or simply visualize, the distances for some AI like attack, roam, escape etc ... a plugin that could show the distance in the editor before running the game would just rock.

[Josh]

In the future, sure.

[AnthonyPython]

  On 2/11/2015 at 5:53 AM, Josh said:

There's other stuff that will make a bigger impact with less effort, so this is not the highest priority right now. The stuff I think really matters is carving, CSG vertex manipulation, vegetation, decals, networking, roads.

 

ALL of that sounds awesome josh leadwerks is feeling more and more like the source engine, but 10 times better.

 

do you think that at some point we will be able to send steam achievement info and stuff in LUA at any point of time without having to use the c++ version? (maybe a plugin?) also a random map generator would great to have in the future