Signal is integer, may be from 0 to 100

This part of the description is misleading because there are no signal inputs involved in this katas; the program takes no inputs and generate some outputs. In fact it probably doesn't even need to be mentioned since this will not affect testing in any way (as tests have handled this already).

This is a poorly written issue. Besides, limiting the range of input is not an issue at all.

Shouldn't the register be a generator? The kata design as is is so different from the actual in-game behaviour that it can barely be called as such.

fixed

Add "integer" in desc
Check please

Fixed

@author: This should be in specification:

The last operation is converting this binary number to decimal and return result!

It's not mentioned that the resulting slice should be converted back to a decimal integer.

It's not mentioned what should be done if the slice ends up being empty.

slice n digits at start and f digits from end

This statement means "take n first elements and last f elements" which is the opposite of what the task is.

Function name should be in snake_case.

Sample tests should explicitly import the test framework and solution.

Fixed!

(Python, at least) The description only refers to acc and p0 registers, however in many random tests appears a p1 register and we're not told how to handle this:

mov 10 p1;mov acc p1;add 7;mov acc p1;add 3;mov acc p1;slp 5;slp 8
[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] should equal [10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10]

@akaipureya: no, adding comparisons or not won't change anything

"What do you mean?"

I meant: is the user supposed to implement different functions? or are those (the example you gave before, like store(100).in(p0)) still provided as strings?
If you still have strings in mind to achieve deduplication of your kata at that point in the dicussion, I guess you just don't understand my point about why there is an underlying duplicacy problem in the first place. In that case, I'd just advise you to drop the idea about authoring this kata (and the series). Sorry, I know it's a bit brutal, but that will spare you a lot of work that will most likely end up in disappointment and "harsh" discussions with other users here, because there aren't a lot of chances that the kata gets approved.

Maybe you should take some more months solving tasks, digging into the beta process as a solver, to see how it goes and to get a better idea of what might go well or not when you'll author kata on your side. And maybe then give another go at authoring.
But don't get me wrong about the work you already provided! What you did so far is rather a good job! The problem is the duplicacy aspect only (see documentation) and the fact that the specific topic you chose for your kata is most likely a dead end about diversification of the task. You're out of luck on that part, for a first authored kata... :s

@FrameMuse: I didn't play to that game, so I don't know what you're suggesting.

cheers all