-
...ay be that you found something others missed or that you did not include a merger others included, eventually the cube(s) are looked over by scouts/scythes o
...found one. You can split the points with another player if you found the merger together. If you intend to hunt for mergers please read this [http://blog.e
19 KB (3,313 words) - 05:21, 30 January 2019
-
...rtificial Intelligence|Artificial Intelligence (AI)]] corrects any problem merger. However, some segments still contain mergers even after being split, whic
2 KB (361 words) - 04:49, 20 July 2019
-
...ide of the cube, the player should remove the segment that attaches to the merger and continue to trace the good part of the branch to completion.
...chat if they are having a difficult problem that they need assistance on. Merger reports or other questions can also be emailed to [mailto:support@eyewire.o
5 KB (893 words) - 16:02, 5 August 2019
-
...r mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
...dd some "dust" that exits the cube in the same spot as the branch with the merger so that the branch will continue to grow.
5 KB (828 words) - 03:27, 31 January 2019
-
*This weight is used to fix a [[Mergers|merger]], missing branch, or missing nub. Their reap will also overwrite the conse
*Some cubes will be frozen when there is a serious merger in the cube that cannot be removed right away.
4 KB (715 words) - 19:26, 13 August 2019
 | File:No borders.png ...the neurons has caused the AI to fuse the two segments together creating a merger.
(1,875 × 856 (281 KB)) - 16:27, 13 June 2014 |
 | File:Merger in the trace.jpg ...merger segment leaving a gap. Leaving the blue line branch would create a merger.
(1,032 × 948 (233 KB)) - 16:59, 13 June 2014 |
-
...r mergers the exit the cube, the player may leave out the segment with the merger and continue their trace as normal.
In the event that the players create a merger, [[Player_Roles#The_Order_of_the_Scythe|Scythes]] or an [[Player_Roles#Admi
5 KB (942 words) - 02:48, 16 November 2019
 | File:Royal mess.jpg ...eck of a royal mess of an AI merger. Because of the no-borders the AI seed merger is one single fused segment that cannot be removed by admins. It has been t
(1,860 × 864 (188 KB)) - 10:06, 14 June 2014 |
 | File:CUTCB.jpg ...bes removed by an admin probably because they contained a non-removable AI merger.
(1,592 × 828 (230 KB)) - 00:08, 17 June 2014 |
 | File:No-borders player merger.jpg ...ch/nub/etc rounder and fuller as they do NOT belong and may lead to larger merger creation.
(2,000 × 323 (344 KB)) - 11:16, 2 July 2014 |
-
'''Merger:'''
10 KB (1,682 words) - 08:45, 23 October 2016
-
A trace going backward from the point of a [[The_Eyewire_Lexicon#M|merger]], allowing one to see that the piece in question is not part of the cell b
...as many as eight iterations. This is important to know when correcting a merger or adding a missing part of the trace.
37 KB (6,387 words) - 21:17, 13 March 2019
-
:Merger of your code into other extensions with duplicate or similar purposes — i
...any extensions whose code you borrow from — especially when performing a merger.
2 KB (315 words) - 22:47, 29 September 2015
