Whoa woah Jolan! No need for that complex setup.
I've got the idea how to make it short with coding without physics. Just 4 logic cards required each grid square:
Distance Operator: Panel (target 1 is the character; target 2 is the grid tile - when the character is landing on a grid square, the panel distance has to be ZERO otherwise the wall blocking of that tile won't work)<-operand 1--Two-input operator: Equals ZERO<-Enabled--Interval Trigger: 1 tick--->State Event: Off---> (targets the controller directions)
What do you mean by 'each grid square'? Like moving your piece one square = 1 step?Originally Posted by Blastergamer
It looks complex but it's just a few cards x4. What you're looking for could prolly be done easier, I was just inspired by the post to jot this down![]()
The shortest possible way to disable character passing through walls without using physics in grid form: https://docs.google.com/drawings/d/1...B6OAJM8Ds/edit
It does have 1 downside, see NOTE in the document.
you will just need a physics joint then go to object properties and set type to slider make sure you make the slider arrows point up and down after then set properties to advanced after set target 1 to a object with no physics then target 2 to the water then go to linear settings then linear motor enable the motor now just mess with the -3.00 and the 3.00 to see which way the water goes hope this is easier for you all?Originally Posted by rlmergeuser Go to original post
Let's see if this sharing thing works. My first attempt in making these drawings.
This is the HSB to RGB converter:
https://docs.google.com/drawings/d/1...it?usp=sharing
Thanks, going to save that now to use it easier in the future. You are like a math wizard..Originally Posted by mutetus Go to original post
edit: I'll wait until some patch comes out that stops my 360 from freezing every 10 seconds when I try to select the vectors..![]()
i know that feeling rishaan, i found if your attempt to delete one thats in use it will create crashes further down the line, it sux i have to be damn careful (instead of carefree) when using them!
i posted this method to crash the game to support, i do not recommend trying this at home, i thought i'd just highlight it
in the editor:
place two "vector object info" (not connected to anything)
place a "Vector operator" set it to "N Vectors" and target the two "vector object info"
now delete the "Vector operator" and replace it, again re-target the two "vector object info"
now point one of the "vector object info" target to an object and the console will crash back to dash board every time (i just pointed it to the other "vector object info"), note: two was the minimum number of "vector object info" i found it needed to crash the editor.
i recommend not using the N Vector option at all until its fixed.
and daaamn mutetus, awesome