Azazil00

Hi, sorry it's been so long. I haven't had time to play, let alone create something to show you, until now that is. Here's a video of a small example of exactly what I'm doing to get this result. Sorry for the poor quality.

I know that I can use the event "On added to inventory" instead, but I want the player to have to hold this item specifically to be able to use the skills because otherwise the animations would look weird.

I noticed this a while ago when making certain weapons have skills with them and whenever the skill would be on a different spot than where the item would be in the inventory bar, it would equip whatever item was in that spot, or just unequip the item I currently had when I used the skill. Forgive me, This is quite hard to explain. What I'm talking about is the two different Hotbars. The one for skills and the one for inventory items. Selections made in the Skill hotbar seem to also select things in the inventory hotbar. This is quite annoying when you want to have certain items give you certain skills because as soon as you use a skill in your hotbar that just happens to be on a different spot than where your item is in the inventory bar, it unequips the item that gives you the skill and makes you have to re-equip it to give the skill back. I hope this made sense. Please let me know if there is anything I can clarify. Thank you.

Every now and then, when I'm editing my scripts, the zoom function just stops working and sometimes will randomly return, but a lot of the time it won't. It's rather frustrating as some of my scripts are pretty large. I'm posting it to try and see if it could be any problem on my end. Thanks!

UPDATE! This is probably the answer to many people's scripts and questions! So I've recently learned how I think you can reference the player in any script, even those without events that reference the player. All you have to do is make a "Global Storage" game logic, edit its script, then create a variable called "Player" inside it. After that, go into a "Player Spawn Point" script, grab the "On Player Created" event, and set the variable "Player" to the Player that the spawn point creates. The global storage gives you global variables, which means they can be used in any script from what I can tell. This means you can reference that "Player" variable after in any script and it will actually be referencing your player! I hope this helps, I know it definitely helps me!

So to create a better reply to this topic and clear some things up to maybe educate a few folks, I want to clarify how I actually reference players in my scripts. But firstly, I want to clarify what I initially made this post about so as to not cause any confusion. I made this post because I was trying to throw the "Iron Spike" entity in a specific orientation that made it look like the spike is flying toward the direction being thrown. I thought I had to manually reference the player and set the rotation and all that after the entity was thrown, but it turns out you can just set the rotation of the entity before you reference it in your entity template. This will set its default orientation. Now anyway, back to the topic of the discussion. How do I reference the player in scripts? Well ultimately, I think you have to start with an event that has either the "Player" or "Trigger Entity" already referenced. So I'm still not sure if there is a way to reference the player in a script that has no default connection to the player. What I like to do is make magic staves and other weapons that give their wielder abilities depending on what attack they use. To begin, I always start my scripts in the staff that I am referencing. This way you gain access to the "On Melee Attack" event, which has three references: Trigger Entity, Attack Type, and Combo Sequence. I never use Combo Sequence because, quite frankly, I don't know how, but I always use the first two. Trigger Entity is just the Entity that Triggered the attack, AKA the player who attacked with the staff. Attack Type is exactly that. There are three attack types, Light, Heavy, and Jump attacks. So after I grab the "On Melee Attack" event, I will then make three "IF" statements to tell what attack I am doing. Here, you can get a reference of the Attack Type and ask if it is = to either a light, heavy, or jump attack to do a task. After I set up my "IF" statements, I then fill them with instructions I've made. (Or I do now at least. My old methods of making staves did not involve Instructions and were much more messy.) Instructions are just a block of code that you can call later and anything inside is executed. It's pretty much a time savor and organization tool, and a very useful one at that. The Instructions have a name of your choosing, and you can also add in references of your choosing too, but these do not automatically reference anything you like. For example, if you create a reference named "Player" it does not automatically reference the player. When calling the Instruction later, you have to assign a value to this reference, meaning you already have to have reference to the player to assign the player to the Reference "Player". All a Reference is is a reference to a Variable of some kind, whether that be your player character, some other Entity, or Item, Game Logic, Number, whatever it may be. Here, you can see my instructions have a single reference beside their names. This reference is called "Player" but it actually has no value, but I assign the "Trigger Entity" to it later. Inside the Instructions are just simply a few particle effects, sound effects, a raycast command, and a variable to hold the direction of the raycast. Anytime you want to reference the player in this script, just drag the "Player" reference to the spot you want. Don't worry about the names of the instructions, you can call them whatever you like, I called mine here "Gust" and "Wind Blast" because I am making a "Wind" based magic staff. Also, usually, I will use a throw command instead of a raycast, but they are set up and function almost entirely the same way. When you call your instructions in the "IF" statements, you just drag the "Trigger Entity" into the open spot next to "Player" and viola! <--- This is what your "On Melee Attack" event should look like at the end.

You talked about spawning in the turret by placing an item, would you care to elaborate as to how to actually do that? I've made a "magic" based turret and want to have a skill that spawns in the turret, but I'm unsure how to spawn the turret as a whole and have it still function correctly.

So I have recently discovered skills, and there is a way to activate "Aim Mode" in a skill but this may not be what you are looking for. Its just a modal state in a skill that makes it activate aim mode like if you were using a gun whenever you equip the skill.

It happened right before I posted that

I was trying to edit a path, and when I was done it wouldn't exit the editing mode. Neither the Esc key or the "Done" button would work

So I was trying to make script with a Crude mace that, on a heavy attack, would launch a large rock forward to hit and damage an opponent. I have made similar scripts a multitude of times, but I wanted this one to deal crushing damage since it is launching a large boulder. I noticed that when I set the damage type to crushing in the throw command, nothing would happen, and nothing in the "On entity hit" and "On ground hit" parts of the throw command, such as particle effects and sounds, would happen either. I tested the same script on other weapons and it was providing the same results, so I changed the damage type next, and after changing just the damage type to Pure, everything started working as intended.

Alrighty, thank you!

So I'm currently trying to create a skill that launches a projectile, and I want the projectile to have a trajectory in an arc shape, like if I hurled a large boulder. So to do this, I've got gravity enabled, and I wanted to utilize the vertical Angle Delta to shoot the projectile upward at a small angle and have gravity pull it down. From the looks of it, the angle you put in only works depending on what horizontal direction you are facing. On one horizontal axis, facing one direction, the angle is correct and positive. If you change direction on the same axis (turn 180 degrees), the angle then becomes negative and shoots the projectile straight into the ground. If you look to either direction on the other horizontal axis (turn 90 or -90 degrees) it seems that the angle turns to zero. I think something may be going on in the code that makes this work, but I am posting it here instead of on the bugs page because I am unsure if this is intended or not. If it is intended and I am misinterpreting how to use Vertical Angle Delta when shooting a projectile in the skill editor, please explain to me how this parameter actually works, as the Horizontal Angle Delta seems to work as intended (or at least how I would intend it).

Sorry this is so late of a reply, but it seems that with the latest update that this has been fixed. Thank you very much!

There is a better way than using the reference point. It's what I use to make some magic weapons and things. You'll need to be able to reference the player in the visual script, so you'll need to be able to get your characters position and rotation. all you need to do is copy the Position tab in this picture. The picture is basically an example of a particle effect playing in front of the caster at a set distance and height. it is basically getting the position of your player and adding a set value for distance and height in the direction you're facing. I the VECTOR tab, X and Z are what is getting your rotation. The Y value is how high off the ground you want your point to be. The last number in the Position tab is how far you want your point to be in front or (if negative) behind your character. Extra Explanation: in the VECTOR tab X and Z are getting the Sin and Cos of the Y value of your character's rotation. The Y value of your character's rotation is the degree at which your character is rotated. When you plug the Sin in the X spot and the Cos in the Z spot, they cancel out to give you the direction you're facing. There is another post in these forums that explains that better, something about throwing a ball or something.