Koji - Revision history

Lachesis at 19:20, 20 January 2013

2013-01-20T19:20:20Z

← Older revision		Revision as of 19:20, 20 January 2013
Line 7:		Line 7:

	===Koji Arrives! Koji vs. Akwende===		===Koji Arrives! Koji vs. Akwende===
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji in an attempt to distance himself from the community perception of the former. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[~~Greg~~ Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji in an attempt to distance himself from the community perception of the former. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Alexis Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) with the intention of determining what features he implemented (and if possible, how to implement them), while pretending to be an admirer of his work at the suggestion of several members of the community[http://www.digitalmzx.net/forums/index.php?showtopic=1274&st=0&#entry12090]. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende.) Koji asked about MZXAk 2, discovering it to be near completion. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with only a fraction of the amount of work hours necessary to complete it. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). In reality, it was likely more Koji who was developing with the intent of coercing Akwende into releasing MZXAk 2. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende), it was not derived from the MZXAk 2.0 source (instead derived from MZXAk 1.0), nor was it feature compatible (with the exception of some , causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's, all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation, along with the SMZX mode from MZX Ak 1.0 (to be readded in a later version); this might have been because features cost a premium in available memory, which was highly limited. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inability to get all of his code working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.		In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) with the intention of determining what features he implemented (and if possible, how to implement them), while pretending to be an admirer of his work at the suggestion of several members of the community[http://www.digitalmzx.net/forums/index.php?showtopic=1274&st=0&#entry12090]. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende.) Koji asked about MZXAk 2, discovering it to be near completion. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with only a fraction of the amount of work hours necessary to complete it. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). In reality, it was likely more Koji who was developing with the intent of coercing Akwende into releasing MZXAk 2. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende), it was not derived from the MZXAk 2.0 source (instead derived from MZXAk 1.0), nor was it feature compatible (with the exception of some , causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's, all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation, along with the SMZX mode from MZX Ak 1.0 (to be readded in a later version); this might have been because features cost a premium in available memory, which was highly limited. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inability to get all of his code working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.

Kuroneko: /* Koji Today */

2010-11-30T06:51:06Z

Koji Today

← Older revision		Revision as of 06:51, 30 November 2010
Line 21:		Line 21:
	While Koji is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for signing up and then dropping out before they start.		While Koji is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for signing up and then dropping out before they start.

	Koji has worked on several games, with his most well down being Chronostodian, a game that has been in progress from 2003 to early 2006, and is all but abandoned today. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew, for a game that has had no clear progress since it was announced. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him Koji is considered a profoundly unlucky person. A meme existed at one point where, after being affected by a serious bout of misfortune, one would consider themselves to be 'koji'd'.		Koji has worked on several games, with his most well down being Chronostodian, a game that has been in progress from 2003 to early 2006, and is all but abandoned today. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew, for a game that has had no clear progress since it was announced. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him Koji is considered a profoundly unlucky person. A meme existed at one point where, after being affected by a serious bout of misfortune, one would consider themselves to be 'koji'd'. In 2009, Koji revealed that he had mostly been making up his misfortunes, and [[Leaving Forever\|Left Forever]].

	{{NeedsPeerReview}}		{{NeedsPeerReview}}

Lancer-X: More edits.

2008-02-04T01:25:21Z

More edits.

← Older revision		Revision as of 01:25, 4 February 2008
Line 14:		Line 14:
	Over the next couple of years Koji maintained a quiet role in the background of the MegaZeux community, never sparking much attention. He later admitted that he deliberately tried to avoid conflict and come off as non-argumentative so that people wouldn't realize he was Artith. This facade eventually wore off however: towards fall of 2003 Exophase started noticing that Koji was (and still is) quick to offer explanations for topics he was not adequately knowledgeable of, or at least not capable of explaining in a sensible fashion. In less than kind words Exophase eventually shot off at him for it (after Koji said that C++ was like C with a few extra features and that objects were like enhanced functions [http://www.digitalmzx.net/forums/index.php?showtopic=6445]), which sparked defensive retaliation from Koji. Exophase responded by noting that Koji was behaving a lot like Artith was, and that in fact he was starting to wonder if Koji was Artith all along. This mention prompted heavy denial and hostility on Koji's part, which made some community members even more suspicious. A good deal of evidence was gathered, comparing writing style, behavior, and several personal connections between Koji and Artith, although much of this was deemed circumstantial. The crux of the debate was the discovery of a mis-crediting of one of Koji's alleged works to Artith, and Koji's possession of the same ultra-obscure video card that Artith had complained about in the past. Koji continued to deny being Artith and provided weak rationalizations to counter the evidence presented. Eventually the debate reached critical mass; some administrators such as [[Esdemo1]] insisted that Koji no longer be pressured since it couldn't be proven beyond any doubt that he was Artith (Esdemo1 personally refused to believe that he was, but also maintained that if he was then he should be banned permanently). Koji himself went into a complete flame rage, and received due criticism specifically for his current behavior, contrary to any suspicions. Koji was eventually paroled, and Exophase gave up trying to get him to admit that he was Artith, conceding that there wasn't enough proof to do anything either way.		Over the next couple of years Koji maintained a quiet role in the background of the MegaZeux community, never sparking much attention. He later admitted that he deliberately tried to avoid conflict and come off as non-argumentative so that people wouldn't realize he was Artith. This facade eventually wore off however: towards fall of 2003 Exophase started noticing that Koji was (and still is) quick to offer explanations for topics he was not adequately knowledgeable of, or at least not capable of explaining in a sensible fashion. In less than kind words Exophase eventually shot off at him for it (after Koji said that C++ was like C with a few extra features and that objects were like enhanced functions [http://www.digitalmzx.net/forums/index.php?showtopic=6445]), which sparked defensive retaliation from Koji. Exophase responded by noting that Koji was behaving a lot like Artith was, and that in fact he was starting to wonder if Koji was Artith all along. This mention prompted heavy denial and hostility on Koji's part, which made some community members even more suspicious. A good deal of evidence was gathered, comparing writing style, behavior, and several personal connections between Koji and Artith, although much of this was deemed circumstantial. The crux of the debate was the discovery of a mis-crediting of one of Koji's alleged works to Artith, and Koji's possession of the same ultra-obscure video card that Artith had complained about in the past. Koji continued to deny being Artith and provided weak rationalizations to counter the evidence presented. Eventually the debate reached critical mass; some administrators such as [[Esdemo1]] insisted that Koji no longer be pressured since it couldn't be proven beyond any doubt that he was Artith (Esdemo1 personally refused to believe that he was, but also maintained that if he was then he should be banned permanently). Koji himself went into a complete flame rage, and received due criticism specifically for his current behavior, contrary to any suspicions. Koji was eventually paroled, and Exophase gave up trying to get him to admit that he was Artith, conceding that there wasn't enough proof to do anything either way.

	About half a year later, in the summer of 2004, Koji gave Exophase a PayPal donation out of consideration for his work on MZX; this was done in spite of the animosity present. The donation actually served a dual purpose: it contained Koji's real name, which was Artith's real name. Exophase didn't actually realize this because he never knew what Artith's name was, but Koji spelled it out for him. They talked in private, where Koji admitted that he really wanted to be proven wrong all along because he couldn't stand constantly pretending anymore. Exophase urged Koji to come clean to the community, insisting that he would be forgiven. Koji was reluctant but eventually proceeded to do so, and he was generally forgiven.		About half a year later, in the summer of 2004, Koji gave Exophase a PayPal donation out of consideration for his work on MZX and as a peace offering; this was done in spite of the animosity present. The donation actually served a dual purpose: it contained Koji's real name, which was Artith's real name. Exophase didn't actually realize this because he never knew what Artith's name was, but Koji spelled it out for him. They talked in private, where Koji admitted that he really wanted to be proven wrong all along because he couldn't stand constantly pretending anymore. Exophase urged Koji to come clean to the community, insisting that he would be forgiven. Koji was reluctant but eventually proceeded to do so, and he was generally forgiven.

	===Koji Today===		===Koji Today===
Line 21:		Line 21:
	While Koji is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for signing up and then dropping out before they start.		While Koji is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for signing up and then dropping out before they start.

	Koji has worked on several games, with his most well down being Chronostodian, a game that has been in progress ~~since at least~~ 2003. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew, for a game that has had no clear progress since it was announced. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him Koji is considered a profoundly unlucky person.		Koji has worked on several games, with his most well down being Chronostodian, a game that has been in progress from 2003 to early 2006, and is all but abandoned today. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew, for a game that has had no clear progress since it was announced. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him Koji is considered a profoundly unlucky person. A meme existed at one point where, after being affected by a serious bout of misfortune, one would consider themselves to be 'koji'd'.

	{{NeedsPeerReview}}		{{NeedsPeerReview}}

Lancer-X: Some polishing, incorporating some of Koji's previous changes which were reverted.

2008-02-04T01:18:18Z

Some polishing, incorporating some of Koji's previous changes which were reverted.

← Older revision		Revision as of 01:18, 4 February 2008
Line 7:		Line 7:

	===Koji Arrives! Koji vs. Akwende===		===Koji Arrives! Koji vs. Akwende===
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji in an attempt to distance himself from the community perception of the former. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) with the intention of determining what features he implemented (and if possible, how to implement them), while pretending to be an admirer of his work. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende)~~. After learning what he wanted to know~~ about MZXAk 2, Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with only a fraction of the amount of work hours necessary to complete it. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). In reality, it was likely more Koji who was developing with the ~~sole~~ intent of ~~preempting~~ Akwende ~~and gaining respect within the community~~. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende), it was not derived from the MZXAk 2.0 source (instead ~~it was based off of~~ MZXAk 1.0), nor was it feature compatible (~~although it had similar features)~~, causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's, all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation, along with the SMZX mode from MZX Ak 1.0; this might have been because features cost a premium in available memory, which was highly limited. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inability to get all of his code working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.		In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) with the intention of determining what features he implemented (and if possible, how to implement them), while pretending to be an admirer of his work at the suggestion of several members of the community[http://www.digitalmzx.net/forums/index.php?showtopic=1274&st=0&#entry12090]. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende.) Koji asked about MZXAk 2, discovering it to be near completion. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with only a fraction of the amount of work hours necessary to complete it. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). In reality, it was likely more Koji who was developing with the intent of coercing Akwende into releasing MZXAk 2. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende), it was not derived from the MZXAk 2.0 source (instead derived from MZXAk 1.0), nor was it feature compatible (with the exception of some , causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's, all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation, along with the SMZX mode from MZX Ak 1.0 (to be readded in a later version); this might have been because features cost a premium in available memory, which was highly limited. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inability to get all of his code working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.

	===Koji Under Suspicion===		===Koji Under Suspicion===

Lancer-X: Koji, stop editing your own wiki page.

2008-02-04T00:48:21Z

Koji, stop editing your own wiki page.

Show changes

Koji: and that's all the polishing I'm up to right now.

2008-02-03T23:41:57Z

and that's all the polishing I'm up to right now.

← Older revision		Revision as of 23:41, 3 February 2008
Line 1:		Line 1:
	'''Koji''' is a member of the [[MegaZeux]] community and has been since at least the year 1999. During this time he has had some well known bouts with community administrators and ops, in particular [[Exophase]].		'''Koji''' is a member of the [[MegaZeux]] community and has been since at least the year 1999. During this time he has had some well known bouts with community administrators and ops, in particular [[Exophase]]. For unknown reasons koji doesn't capitalize his own name unless it begins a sentence.

	==The Complicated Case of Koji==		==The Complicated Case of Koji==
Line 12:		Line 12:

	===Koji Under Suspicion===		===Koji Under Suspicion===
	Over the next couple of years ~~Koji~~ maintained a quiet role in the background of the MegaZeux community, never sparking much attention. He later admitted that he deliberately tried to avoid conflict and come off as non-argumentative so that people wouldn't realize he was Artith. This facade eventually wore off however: towards fall of 2003 Exophase started noticing that ~~Koji~~ was (and still is) quick to offer explanations for topics he was not adequately knowledgeable of, or at least not capable of explaining in a sensible fashion. In less than kind words Exophase eventually shot off at him for it (after ~~Koji~~ said that C++ was like C with a few extra features and that objects were like enhanced functions [http://www.digitalmzx.net/forums/index.php?showtopic=6445]), which sparked defensive retaliation from ~~Koji~~. Exophase responded by noting that ~~Koji~~ was behaving a lot like Artith was, and that in fact he was starting to wonder if ~~Koji~~ was Artith all along. This mention prompted heavy denial and hostility on ~~Koji~~'s part, which made some community members even more suspicious. A good deal of evidence was gathered, comparing writing style, behavior, and several personal connections between ~~Koji~~ and Artith, although much of this was deemed circumstantial. The crux of the debate was the discovery of a mis-crediting of one of ~~Koji~~'s alleged works to Artith, and ~~Koji~~'s possession of the same ultra-obscure video card that Artith had complained about in the past. Koji continued to deny being Artith and provided weak rationalizations to counter the evidence presented. Eventually the debate reached critical mass; some administrators such as [[Esdemo1]] insisted that ~~Koji~~ no longer be pressured since it couldn't be proven beyond any doubt that he was Artith (Esdemo1 personally refused to believe that he was, but also maintained that if he was then he should be banned permanently). ~~Koji~~ himself went into a complete flame rage, and received due criticism specifically for his current behavior, contrary to any suspicions. Koji was eventually paroled, and Exophase gave up trying to get him to admit that he was Artith, conceding that there wasn't enough proof to do anything either way.		Over the next couple of years koji maintained a quiet role in the background of the MegaZeux community, never sparking much attention. He later admitted that he deliberately tried to avoid conflict and come off as non-argumentative so that people wouldn't realize he was Artith. This facade eventually wore off however: towards fall of 2003 Exophase started noticing that koji was (and still is) quick to offer explanations for topics he was not adequately knowledgeable of, or at least not capable of explaining in a sensible fashion. In less than kind words Exophase eventually shot off at him for it (after koji said that C++ was like C with a few extra features and that objects were like enhanced functions [http://www.digitalmzx.net/forums/index.php?showtopic=6445]), which sparked defensive retaliation from koji. Exophase responded by noting that koji was behaving a lot like Artith was, and that in fact he was starting to wonder if koji was Artith all along. This mention prompted heavy denial and hostility on koji's part, which made some community members even more suspicious. A good deal of evidence was gathered, comparing writing style, behavior, and several personal connections between koji and Artith, although much of this was deemed circumstantial. The crux of the debate was the discovery of a mis-crediting of one of koji's alleged works to Artith, and koji's possession of the same ultra-obscure video card that Artith had complained about in the past. Koji continued to deny being Artith and provided weak rationalizations to counter the evidence presented. Eventually the debate reached critical mass; some administrators such as [[Esdemo1]] insisted that koji no longer be pressured since it couldn't be proven beyond any doubt that he was Artith (Esdemo1 personally refused to believe that he was, but also maintained that if he was then he should be banned permanently). koji himself went into a complete flame rage, and received due criticism specifically for his current behavior, contrary to any suspicions. Koji was eventually paroled, and Exophase gave up trying to get him to admit that he was Artith, conceding that there wasn't enough proof to do anything either way.

	About half a year later, in the summer of 2004, Koji gave ~~Exophase~~ a PayPal donation ~~out of consideration for his work on MZX; this was done in spite of~~ the animosity ~~present. The donation actually~~ served a dual purpose: it contained ~~Koji~~'s real name, which was Artith's real name. Exophase didn't actually realize this ~~because he never knew what Artith's name was~~, but ~~Koji~~ spelled it out for him. They talked in private, where ~~Koji~~ admitted that he really wanted to be proven wrong all along because he couldn't stand constantly pretending anymore. Exophase urged ~~Koji~~ to come clean to the community, insisting that he would be forgiven. Koji was reluctant but eventually proceeded to do so, and he was generally forgiven.		About half a year later, in the summer of 2004, there was a call for donations to support Exophase's work [http://www.digitalmzx.net/forums/index.php?showtopic=7814&hl=Exophase++Donations]. Koji gave a PayPal donation despite the animosity held between Exophase and him which served a dual purpose: not only was it a peace offering it also served as proof in a long standing argument. It contained koji's real name, which was also Artith's real name. Exophase didn't actually realize this immediately, but koji spelled it out for him. They talked in private, where koji admitted that he really wanted to be proven wrong all along because he couldn't stand constantly pretending anymore. Exophase urged koji to come clean to the community, insisting that he would be forgiven. Koji was reluctant but eventually proceeded to do so, and he was generally forgiven.

	===Koji Today===		===Koji Today===
	The overall level of annoyance towards ~~Koji~~ has since subsided, but he still has a reputation for providing explanations and advice where he really shouldn't. The administration generally agrees that he has a penchant for speaking without thinking. He has been known to leave nodes on this wiki that are of questionable content, such as "... it's Tetris." or "Koji is a koji", and at other times lacking in quality of writing or factual content.		The overall level of annoyance towards koji has since subsided, but he still has a reputation for providing explanations and advice where he really shouldn't. The administration generally agrees that he has a penchant for speaking without thinking. He has been known to leave nodes on this wiki that are of questionable content, such as "... it's Tetris." or "Koji is a koji", and at other times lacking in quality of writing or factual content.

	While ~~Koji~~ is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for signing up and then dropping out before they start.		While koji is not well known for any major MegaZeux releases aside from MZX 2.60 itself, he is a relatively respected [[Robotic]] programmer who has demonstrated his skills in some impressive [[engine\|engines]] (most of all his "voxel" engine which has perspective correction and height mapping, ironically this is one of his simpler engines). Koji has participated in a few [[Day of Zeux]] competitions, although he is generally known for either not completing or signing up and then dropping out before they start.

	Koji has worked on several games, with his most well ~~down~~ being Chronostodian, a game that ~~has been~~ in progress ~~since~~ at least 2003. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew~~, for a game that has had no clear progress since it was announced~~. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him ~~Koji~~ is considered a profoundly unlucky person.		Koji has worked on several games, with his most well known being Chronostodian, a game that was in progress from at least 2003 to early 2006 but is all but abandoned. It is often considered one of the best examples of [[vaporware]] in the community, long since surpassing [[Sivion]], and only rivaled by [[Starflight MZX]]. Koji has kept a journal following the game for years. Every now and then he will announce that he's adding a complex new feature or system to it, which has eventually led to him being criticized for biting off more than he can chew. He is also known for having lost his work on many occasions due to computer failure. In fact, because of this and several other tragedies that follow him koji is considered a profoundly unlucky person and a meme existed at one point where people who found themselves to be particularly unlucky at a particular instance would say "I've been koji'd"

	===Future Koji===		===Future Koji===
	~~Lets~~ hope for the best		Koji has at several instances claimed that he would present himself to be more respectable, however on most occasions his efforts would either be ridiculed or end up short lived. Koji still maintains that he's getting ''better'' however progress is by no means constant. We can only hope for the best.

	{{NeedsPeerReview}}		{{NeedsPeerReview}}

Koji at 23:07, 3 February 2008

2008-02-03T23:07:33Z

← Older revision		Revision as of 23:07, 3 February 2008
Line 7:		Line 7:

	===Koji Arrives! Koji vs. Akwende===		===Koji Arrives! Koji vs. Akwende===
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as ~~Koji~~. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because ~~Koji~~ was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that ~~Koji~~ was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, ~~Koji~~ named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 ~~Koji~~ implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), ~~Koji~~ figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that ~~Koji~~ manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). ~~koji asked~~ about the source ~~when prompted by someone in #mzx~~ and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion ~~Koji~~ proceeded to tell Akwende off admitting that he was going ~~to release~~ his own version ~~now~~, with the same functionality of MZXAk2.0 and more. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of ~~Koji~~'s work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent ~~Koji~~ from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). ~~"In reality, it was likely more Koji who was developing with the sole intent of preempting~~ Akwende ~~and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going~~ to release MZXAk 2.0 until koji approached him (which he ~~regretted fairly quickly~~) ~~but koji admits he did work on the MZX 2~~.~~60 partly for respect but also because there were features he's like to have added. Nonetheless, despite~~ MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering ~~Koji~~'s boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting and MZXAk2.0 was publicly thrown out almost immediately upon release), nor was it feature compatible (although it had similar features some of which were based on Akwende's designs made available in his source), causing the first real fork in MZX development. Because Exophase supported ~~Koji~~'s branch over Akwende's (~~of course supporting of an Akwende version would have not looked very good at the time,~~ and ~~koji's version didn't use up as much memory~~), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time ~~however~~ some people suggested to remove it as it was ''not worth ~~keeping'' however later~~ it was ~~reimplemented~~. 2.60 actually contained some code from [[inmate2993]] and Exophase due to ~~Koji~~'s inexperience in C programming that ~~stopped him from getting all~~ promised features working. ~~Koji~~ released MZX 2.61, which was ~~nothing but~~ a bug fix (2.60 was notoriously buggy)~~; this marked the end of his involvement with the MZX source code~~.		In MZX 2.60 koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel namely Exophase (who admitted responsibility [http://www.digitalmzx.net/forums/index.php?showtopic=1274&st=0&#entry12090]) and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). Koji did ask about the source code of MZXAk2.0 at the suggestion of Exophase and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion koji proceeded to tell Akwende off admitting that he was going releasing his own version of mzx, with the same functionality of MZXAk2.0 and more. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance as a moderator). Akwende had no plan to release MZXAk 2.0 until koji approached him (which he soon came to regret). Despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting and because MZXAk2.0 was publicly thrown out almost immediately upon release), nor was it feature compatible (although it had similar features some of which were based on Akwende's designs made available in the release of his source), causing the first real fork in MZX development. Because Exophase supported koji's branch over Akwende's (For ethical and technical reasons), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up (the smzx hack was actually quite tiny at the time) but because some people suggested to remove it as it was not used enough to be worth the memory that it did take up. SMZX mode was added again in Exophase's release of 2.65 answering to community outcry for the graphical functionality. 2.60 actually contained some code from [[inmate2993]] and Exophase due to koji's inexperience in C programming that inhibited his promised features from working. The end of koji's involvement with the MZX source code was marked with his released of MZX 2.61, which was not much more than a bug fix (2.60 was notoriously buggy).

	===Koji Under Suspicion===		===Koji Under Suspicion===

Koji: /* Koji Arrives! Koji vs. Akwende */

2008-02-03T14:51:18Z

Koji Arrives! Koji vs. Akwende

← Older revision		Revision as of 14:51, 3 February 2008
Line 9:		Line 9:
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more ~~(the idea that I told him I would get it done in a fraction of the time doesn't make sense at all)~~. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). "In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until koji approached him (which he regretted fairly quickly) but koji admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting and MZXAk2.0 was publicly thrown out almost immediately upon release), nor was it feature compatible (although it had similar features some of which were based on Akwende's designs made available in his source), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.		In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more. Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). "In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until koji approached him (which he regretted fairly quickly) but koji admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting and MZXAk2.0 was publicly thrown out almost immediately upon release), nor was it feature compatible (although it had similar features some of which were based on Akwende's designs made available in his source), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.

	===Koji Under Suspicion===		===Koji Under Suspicion===

Koji: /* Koji Arrives! Koji vs. Akwende */

2008-02-03T14:46:09Z

Koji Arrives! Koji vs. Akwende

← Older revision		Revision as of 14:46, 3 February 2008
Line 9:		Line 9:
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more (the idea that I told him I would get it done in a fraction of the time doesn't make sense at all). Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). "In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until he approached ~~Akwende and~~ he admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added.		In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more (the idea that I told him I would get it done in a fraction of the time doesn't make sense at all). Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). "In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until koji approached him (which he regretted fairly quickly) but koji admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added. Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting and MZXAk2.0 was publicly thrown out almost immediately upon release), nor was it feature compatible (although it had similar features some of which were based on Akwende's designs made available in his source), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.

	Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting), nor was it feature compatible (although it had similar features), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.

	===Koji Under Suspicion===		===Koji Under Suspicion===

Koji: /* Koji Arrives! Koji vs. Akwende */

2008-02-03T14:42:21Z

Koji Arrives! Koji vs. Akwende

← Older revision		Revision as of 14:42, 3 February 2008
Line 9:		Line 9:
	Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).		Shortly thereafter (circa summer 2001), in the community's most significant instance of [[identity deception]], Artith rejoined as Koji. Koji claimed to be friends with Artith, whom he spoke of in a mildly denigrating tone. Although he knew many things about Artith that he probably shouldn't have (even explaining that his poor spelling and argumentative attitude was just a very deliberate attempt at trolling) koji contends today that the denigration of ''Artith'' was an attempt to distance himself in peoples minds from his former self either way most people shrugged it off because Koji was relatively agreeable and well to do. One exception was [[Diamond]], who strongly contended that Koji was Artith. Koji quickly gained acceptance as a "new" member of the community by showing an interest in developing MegaZeux as Artith he mused the idea on several occasions but was ridiculed when he asked for help. At the time, most of the former developers working on MZX 2.7 had gotten tired of it, and the few remaining that had any interest at all were split off from [[mzx (channel)\|#mzx]] due to the prior community schism between it and #megazeux. Those with proficient knowledge in C/C++ were at an extreme minimum, and anyone showing any such ability to muddle through [[Greg Janson]]'s source code was immediately embraced. Upon suggestion, Koji named the version he was working on MZX 2.60 which marked a return to "proper" version numbers (as opposed to ones named after the principle author such as MZX 2.51 [[MegaZeux#Spider Versions\|spider versions]] or [[MegaZeux#MZXak\|MZXAk]]).

	In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more (the idea that I told him I would get it done in a fraction of the time doesn't make sense at all). Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). ''In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community.'' claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until he approached Akwende and he admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added.		In MZX 2.60 Koji implemented many features that were hold-overs meant to be implemented in MZXAk 2.0. Since [[Akwende]] openly left the community on bad terms after controversy surrounding his MZXAk 1.0 release (and following behavior), Koji figured that MZXAk would never be released. Koji first called out Akwende on [[DigitalMZX]] asking to have the source so he could finish it, while receiving "very little credit." [http://www.digitalmzx.net/forums/index.php?showtopic=1148&hl=] It later became apparent that Koji manipulatively approached Akwende (on AIM) pretending to be an admirer of his work at the suggestion of several members of the #mzx channel and continued to post excerpts of the AIM chat and receive some direction on what to converse next. Koji seemed to hold an animosity towards Akwende at the time, which was mysterious due to his apparent newness (surprisingly, this didn't tip anyone off either, possibly because he was only one of many people who weren't very happy with Akwende). koji asked about the source when prompted by someone in #mzx and discovered from Akwende that apparently the source for his version was already pretty much completed it's just that it was on some CD that he couldn't find durring the few months prior. Once MZX 2.60 was nearing completion Koji proceeded to tell Akwende off admitting that he was going to release his own version now, with the same functionality of MZXAk2.0 and more (the idea that I told him I would get it done in a fraction of the time doesn't make sense at all). Shortly thereafter, Akwende released MZXAk 2 on DigitalMZX, to much widespread surprise. The community, being much more aware of Koji's work on MZX 2.60, found the timing suspect. Exophase in particular accused Akwende of releasing only to prevent Koji from making him look bad, which sparked furious arguments between the two rivals (Exophase would later come to deeply regret this short-sighted and biased stance). "In reality, it was likely more Koji who was developing with the sole intent of preempting Akwende and gaining respect within the community." claims Exophase, however koji contends that Akwende was not going to release MZXAk 2.0 until he approached Akwende and he admits he did work on the MZX 2.60 partly for respect but also because there were features he's like to have added.

	Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting), nor was it feature compatible (although it had similar features), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.		Nonetheless, despite MZX 2.60 being released several months after MZXAk 2.0 (ironic, considering Koji's boasting that he could develop it in much less time than it took Akwende however to be fair Akwende had a nearly finished copy on CD for several months presumably and had been working on his version much longer than koji had), it was not derived from the MZXAk 2.0 source (instead it was based off of MZXAk 1.0 because that was all that was available to koji upon starting), nor was it feature compatible (although it had similar features), causing the first real fork in MZX development. Because Exophase supported Koji's branch over Akwende's (of course supporting of an Akwende version would have not looked very good at the time, and koji's version didn't use up as much memory), all future versions were derived from MZX 2.60, and the MZXAk 2.0 branch died. (Akwende quietly slid back into the background, before appearing over a year later with humorous concerns of MZXAk 2 support.) The community didn't seem to mind MZXAk 2.0 being thrown out with little explanation. Smzx was thrown out not mainly because of the memory it took up, the smzx hack was actually quite tiny at the time however some people suggested to remove it as it was ''not worth keeping'' however later it was reimplemented. 2.60 actually contained some code from [[inmate2993]] and Exophase due to Koji's inexperience in C programming that stopped him from getting all promised features working. Koji released MZX 2.61, which was nothing but a bug fix (2.60 was notoriously buggy); this marked the end of his involvement with the MZX source code.