This is the latest LukeTools V4

Oh. I also mentioned the LukeTools button disappearing when you switch projects.

@lukeo25 the google drive says I need acess

Not sure why the link borks out like that. Use this zip instead. https://forum.wickeditor.com/uploads/short-url/jIz2zygPQTjEODemi34JAkgFAGj.zip

Works fine now – thanks!

Uhh, I also mentioned the LukeTools button disappearing when you switch projects.

Sorry mate thats a Wick issue. LukeTools has to be loaded each time. I sugest you create a Wick file with it loaded and us that as your start file for each project.

L

But I saidw can you fix it? You would use part of the LukeTOols V3 code to fix it.

LukeTools code only works as an external plugin - usable only once on a project. It needs to be loaded and run everytime. A fork using my js file would fix this. But as the other fork developers don’t want to do that, which is their right. It needs to run once each load. You could build your own fork by downlaoding the Git repository for Wick ( https://github.com/wicklets/wick-editor ) or Candlestick ( https://github.com/Candlestickers/Candlestick ) and follow my instructions to have your own version with LukeTools loading on startup. https://forum.wickeditor.com/uploads/short-url/vM8ldWzbAoc7i64W6a8LXlK1ihv.zip

If you do be sure to share it with others.

L

nothing against luke tools I think they’re pretty great and useful for whoever loves em

But as Baron put it, Luketools is a bit too big of a hurdle and outside the scope of the plans we have laid out and our future vision of Candlestick

And to add another note— Luke tools aren’t integrated into the engine but rather laid over it. Which makes them easier to add in, yep, but will exist on a separate layer and format than our current engine, and respectfully it’s not something we’re considering on adding in right now as we want to aim towards something that’s more engine-integrated, beginner friendly, and follows similar blueprint to our current structure and plans for the tool.

@lukeo25 my tip to you, you should turn luketools into a chrome extension. It’d work with all the wick forks (wick, candlestick, stickmanred’s, etc.) and it’s a better option than needing to maintain an entire new fork.

Actually in our early stages developing Candlestick this was an area I looked into and can help you there if you have any questions on the setup and where to begin
(that said I cannot help with maintaining the tool or answering forum questions on it :sweat_smile: )
Fortunately your code is already written as an add on, in the perfect format for an extension than an engine integration.

So it wouldn’t take much effort to turn it into an extension. I recommend looking into it.

1 Like

What a great idea!
I LOVE IT!

L

1 Like

Luke Tools is now a downloadable Chrome extension.
Check this thread Add LukeTools permanently using this Chrome extension

Can you add a keyboard shortcut to open the Luketools thingy?

He did, If I remember it’s Shift + L, or it’s Shift + Ctrl + L.

Yes it’s Shift + Ctrl + L.

Add a grid and snap feature

1 Like

This would seem like a neat addition!

Add a grid and snap feature

As Luketools sits above the Wick editor stage - it cant get objects to snap to a grid. But I will take a look.

You can do this very easily.

Grid itself just needs a grid path generator, or creating a bunch of lines.

Grid snapping requires some modding of the Cursor Tool, but you can copy and modify it.

Do what Noobfield says.