#Geometry Dash - 15 objects
Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this (especially because of the negative numbers).
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
Explanation:
The top-left trigger (Instant Count 2) checked if the first addend was 0. If it was, it then checked if the second addend was positive or negative. If it was positive, it transferred the value from the second addend to the sum (BF-style, using loops) and if it was negative, it would do the same thing.
The reason why we need to check if the second addend is positive or negative is that we would need to subtract one from the second addend and add one to the sum or add one to the second addend and subtract one from the sum respectively.
If the first addend is not zero, it tests whether it is positive or negative using the process above. After one iteration in the while loop, it tests to see if the first addend is zero and if it is, it does the process described at the beginning of the explanation.
Since Geometry Dash is remarkably similar to BF, you could make a BF solution out of this.
#Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this (especially because of the negative numbers).
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
Explanation:
The top-left trigger (Instant Count 2) checked if the first addend was 0. If it was, it then checked if the second addend was positive or negative. If it was positive, it transferred the value from the second addend to the sum (BF-style, using loops) and if it was negative, it would do the same thing.
The reason why we need to check if the second addend is positive or negative is that we would need to subtract one from the second addend and add one to the sum or add one to the second addend and subtract one from the sum respectively.
If the first addend is not zero, it tests whether it is positive or negative using the process above. After one iteration in the while loop, it tests to see if the first addend is zero and if it is, it does the process described at the beginning of the explanation.
Since Geometry Dash is remarkably similar to BF, you could make a BF solution out of this.
Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this (especially because of the negative numbers).
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
Explanation:
The top-left trigger (Instant Count 2) checked if the first addend was 0. If it was, it then checked if the second addend was positive or negative. If it was positive, it transferred the value from the second addend to the sum (BF-style, using loops) and if it was negative, it would do the same thing.
The reason why we need to check if the second addend is positive or negative is that we would need to subtract one from the second addend and add one to the sum or add one to the second addend and subtract one from the sum respectively.
If the first addend is not zero, it tests whether it is positive or negative using the process above. After one iteration in the while loop, it tests to see if the first addend is zero and if it is, it does the process described at the beginning of the explanation.
Since Geometry Dash is remarkably similar to BF, you could make a BF solution out of this.
#Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this (especially because of the negative numbers).
[![enter image description here][1]][1]enter image description here
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
I'll post an explanationExplanation:
The top-left trigger "soon" (Instant Count 2) checked if the first addend was 0. [1]: If it was, it then checked if the second addend was positive or negative. If it was positive, it transferred the value from the second addend to the sum https://i.sstatic.net/ci97N.png (BF-style, using loops) and if it was negative, it would do the same thing.
The reason why we need to check if the second addend is positive or negative is that we would need to subtract one from the second addend and add one to the sum or add one to the second addend and subtract one from the sum respectively.
If the first addend is not zero, it tests whether it is positive or negative using the process above. After one iteration in the while loop, it tests to see if the first addend is zero and if it is, it does the process described at the beginning of the explanation.
Since Geometry Dash is remarkably similar to BF, you could make a BF solution out of this.
#Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this.
[![enter image description here][1]][1]
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
I'll post an explanation "soon". [1]: https://i.sstatic.net/ci97N.png
#Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this (especially because of the negative numbers).
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
Explanation:
The top-left trigger (Instant Count 2) checked if the first addend was 0. If it was, it then checked if the second addend was positive or negative. If it was positive, it transferred the value from the second addend to the sum (BF-style, using loops) and if it was negative, it would do the same thing.
The reason why we need to check if the second addend is positive or negative is that we would need to subtract one from the second addend and add one to the sum or add one to the second addend and subtract one from the sum respectively.
If the first addend is not zero, it tests whether it is positive or negative using the process above. After one iteration in the while loop, it tests to see if the first addend is zero and if it is, it does the process described at the beginning of the explanation.
Since Geometry Dash is remarkably similar to BF, you could make a BF solution out of this.
#Geometry Dash - 15 objects
Finally done.
15 objects aren't much, but it was still a nightmare to do this.
[![enter image description here][1]][1]
Because I would have to insert 15 images here for how to reproduce this, I just uploaded the level. The level ID is 5216804. The description tells you how to run it and you can copy it since it is copyable.
I'll post an explanation "soon". [1]: https://i.sstatic.net/ci97N.png