God bless U! Thank u for description!

That's very obvious

I think most of this code accomplishes nothing.

Can't do that. Strings are referenced by value. ( If I understand you correctly. )

.

.

Too late anyway. Retirement is final.

Added please resolve.

[S w o r d] is not the usual representation of an array of characters ( I suppose it's supposed to be that ).

"encoded in HEX" ? In ASCII? or in plain numbers? If so, starting from 0 or from 1 ? Please specify that.

Also, specifying the actual task itself might be a good idea. This is a bit vague. Remember, solvers don't know what you don't tell them.

Identifiers should [ in JavaScript; other languages may have other conventions ] be named in camelCase ( unless they're Constructors, which are named in PascalCase ). So Adventure should be adventure.

Maybe I should have to put condition to change/create form original array word "Sword".

Needs random tests. Some guides here:

• https://github.com/Codewars/codewars.com/wiki/Tutorial%3A-Create-Your-First-Kata#write-good-tests-and-utilize-both-fixed-and-random-test-cases
• https://github.com/Codewars/codewars.com/wiki/Kata-Best-Practices#testing

Needs example test cases.

Hi,

Seems you're new to cw, so here are some general guidelines about the comments:

• Issue: problem in the kata itself (description, wrong tests, wrong internal solution...)
• Suggestions: well, I guess that part is clear
• Question anything else that is related to you having a problem solving a kata -> that's you, currently.

When you post issues:

• provide ALL the useful information:
  • language
  • input
  • outputs (actual expected) when relevant
  • error message when relevant
• check, DOUBLE check that this IS an issue, meaning that the problem is in the kata itself and not in your code. If it's in your code, post rather a question
• if you pass this step, you still have to prove/explain what the issue is (and if you can provide fixes, it's even better)

When you post a question: well, most of the above apply too x)

When you post code, use proper github markdown, so that it's readable.

As you can see, you're clearly not facing an "issue" and you don't provide any useful information to help you. Either way, closing. Complete your answer if you want us to be able to provide any kind of help.

cheers