grenade | Cause fires in production | Monitoring library

My background is in SQL but I've been learning Bash to create tools to help non-Linux users find what they need from my Linux system - I am pretty green with Bash, I apologize if this looks a bit dumb.

The goal of the script is to essentially display all directories within the current directory to the user, and allow them to input 1-9 to navigate to lower directories.

My sticking point is that I'm trying to use arrays to define potential filepaths, since in practice new directories will be added over time and it is not practical to edit the script each time a filepath is added.

Here's my prototype so far, currently it navigates into Test1, Test2, or Test3 then echos pwd to prove it is there.

I'm developing a web game in JavaScript and I have a few arrays of objects. For some reason, I'm experiencing this problem: When I randomly select an object from an array:

I try to make a bouncing bullet for a game that should disappear after bouncing 3 times. I thought it's simple, I gave my bullet a variable with the value of 3 and decreased it in my bullet-platform collider by one.

After it didn't work and checked the variable with console.log(), I found out that the variable gets decreased continuously. I tested my other colliders and found out that only the bullet-platform collider do that, while the player-platform, enemy-platform, bullet-player and bullet-enemy collider don't. In addition my function for destroying bullets, when they hit a platform, oddly work fine. My bullets only get destroyed when hitting a platform.

Does anyone have an Idea how to fix that?

Edit: I made a Github repository of my game for better insight. (At least I hope I did, I haven't used Github before.) https://github.com/Kiroho/Game

Edit2: After testing around, I found out that it must have something to do with how I use my ammoGroup class.

I found out that, if I create bullets via ammoGroup (via createMultiple), the collider starts firing for each bullet until I shot them at least once. After all existing bullets are fired once, everything works normally and the collider fires as intended -> only on collision.

My bullet-platform collider

My entire code:

I keep getting 'spell' is not defined.

Please keep in mind I am very new at this. I've mostly been following a tutorial class in Udemy.

I have strange problem with buttons that are requesting for displaying templates on client page.

This is client side code. The main task of entire class is to just enable user to click button, send request and get response with HTML that has been rendered from handlebars template and just paste it in partiuclar place on client side. It works, but only once. After first click and displaying elements, I totally lose any interaction with those buttons. There is no request, and there is no even EventListener for clicking. I get no error. Completely there is no single reaction after clicking.

I'm trying to get this to validate, it's probably a comma or formatting but I can't work it out and it's driving me insane - It doesn't seem to fail initially not sure why it does later on.

For reference: https://umod.org/plugins/server-rewards#adding-an-item

Any help would be appreciated - Thanks in advance.

Ubuntu 16.04
Bash 4.4.20

I'd like to clean up a few of my game configs so the information is neatly stored in columns. Each line has something like:

I have a character that can only turn on the Y-axis, so left and right basically, if up is Vector3.up. The character has a child which is the position where grenades spawn (his right hand), and now I'm trying to figure out how I can calculate the correct rotation for the parent so the child looks exactly at a target, but only "horizontally". The x and z rotation of the parent must be 0. Is there a way to do that? It's fine if the child only looks into the correct direction on the "horizontal plane", but doesn't look up or down to face the target perfectly.

This answer almost does what I want: http://answers.unity.com/comments/1339850/view.html

The only problem is that the resulting rotation is a mix of all three axes, instead of it being just a y-rotation.