RicePigeon

If the author wanted to use english language clips then that's the author's decision. More than likely english is the author's native language and would prefer to hear something that makes sense, instead of inadvertently adding a language that they're not familiar and end up in an embarassing situation where the character ends up saying something like "suck my a-hole" for a Normal move or something.
 
Just move on from it, it's honestly not that big a deal in comparison to stuff that actually matters, like the gameplay.

If the author wanted to use english language clips then that's the author's decision. More than likely english is the author's native language and would prefer to hear something that makes sense, instead of inadvertently adding a language that they're not familiar and end up in an embarassing situation where the character ends up saying something like "suck my a-hole" for a Normal move or something.
 
Just move on from it, it's honestly not that big a deal in comparison to stuff that actually matters, like the gameplay.

If the author wanted to use english language clips then that's the author's decision. More than likely english is the author's native language and would prefer to hear something that makes sense, instead of inadvertently adding a language that they're not familiar and end up in an embarassing situation where the character ends up saying something like "suck my a-hole" for a Normal move or something.
 
Just move on from it, it's honestly not that big a deal in comparison to stuff that actually matters, like the gameplay.

If the author wanted to use english language clips then that's the author's decision. More than likely english is the author's native language and would prefer to hear something that makes sense, instead of inadvertently adding a language that they're not familiar and end up in an embarassing situation where the character ends up saying something like "suck my a-hole" for a Normal move or something.
 
Just move on from it, it's honestly not that big a deal in comparison to stuff that actually matters, like the gameplay.

Just to clarify, the poll wasn't intended to be a determining factor in our final decision, but we wanted to get a feeling of what public opinion on the subject was.

Just to clarify, the poll wasn't intended to be a determining factor in our final decision, but we wanted to get a feeling of what public opinion on the subject was.

Alright, I'm sure many of you are familiar with Archive in recent years and this is something that I have brought up in private with the rest of the staff, but I would like some public feedback regarding a possible change in our policy regarding MFFA links. This thread isn't meant to guarantee a certain outcome, but we feel some public feedback may help influence our final decision.
 
For those of you who are unaware, back in June of 2016, we made the decision to blacklist any and all download links from Mugen Archive in light of their decision to use Adfly as their primary source of revenue. You can read about our reasoning for this decision here.
 
In recent months, however, it would seem that Mugen Archive has turned to another source of ad revenue and have discontinued their use of Adfly/Shortest, thus, no longer posing the security threat that we originally blacklisted them for. Because the sole basis of our decision no longer applies, I feel that it's appropriate to finally lift this ban that has been in effect for the past two years.
 
Others that I have spoken to did have some concerns that could potentially be used against this decision. Notably, the biggest concern deals with Archive's "Community Weekend" events, which temporarily throttle and/or disable downloads for non-registered users, making them unreliable hosting. While this is true, the same could easily be said of other sites like sendspace, which are not currently blacklisted. Unlike sites such as 4shared, which require registration, the same does not apply to Archive, despite the aforementioned limitations. While this may not affect release threads too much, this could be a concern for those hoping to use archive links in collection threads.
 
I just want to reiterate that the conduct of certain MA members, unless they are actively compromising the security of MFFA or its members, shouldn't play a factor in this decision; this deals primarily with the linking to hosted downloads, if a member of MA is caught breaking the rules of MFFA's forums or discord chat, they will be handled with as we would any other user, independently of any other Mugen community they may be associated with.
 
That being said, I would like to know what everyone's thoughts on this idea are.
 

Alright, I'm sure many of you are familiar with Archive in recent years and this is something that I have brought up in private with the rest of the staff, but I would like some public feedback regarding a possible change in our policy regarding MFFA links. This thread isn't meant to guarantee a certain outcome, but we feel some public feedback may help influence our final decision.
 
For those of you who are unaware, back in June of 2016, we made the decision to blacklist any and all download links from Mugen Archive in light of their decision to use Adfly as their primary source of revenue. You can read about our reasoning for this decision here.
 
In recent months, however, it would seem that Mugen Archive has turned to another source of ad revenue and have discontinued their use of Adfly/Shortest, thus, no longer posing the security threat that we originally blacklisted them for. Because the sole basis of our decision no longer applies, I feel that it's appropriate to finally lift this ban that has been in effect for the past two years.
 
Others that I have spoken to did have some concerns that could potentially be used against this decision. Notably, the biggest concern deals with Archive's "Community Weekend" events, which temporarily throttle and/or disable downloads for non-registered users, making them unreliable hosting. While this is true, the same could easily be said of other sites like sendspace, which are not currently blacklisted. Unlike sites such as 4shared, which require registration, the same does not apply to Archive, despite the aforementioned limitations. While this may not affect release threads too much, this could be a concern for those hoping to use archive links in collection threads.
 
I just want to reiterate that the conduct of certain MA members, unless they are actively compromising the security of MFFA or its members, shouldn't play a factor in this decision; this deals primarily with the linking to hosted downloads, if a member of MA is caught breaking the rules of MFFA's forums or discord chat, they will be handled with as we would any other user, independently of any other Mugen community they may be associated with.
 
That being said, I would like to know what everyone's thoughts on this idea are.
 

Game updated to version 2.6.0.2
 
Full version download:
http://www.mediafire.com/file/tq7fi4luws3ehaf/Touhou_Gensokyo_Reloaded_v2.6.0.2_FULL.zip/file
 
Update patch (Requires version 2.6.0 or higher):
http://www.mediafire.com/file/ie9urk5qeri9rn6/Touhou Gensokyo Reloaded v2.6.0.2 update patch.zip

 
 

This Rem, hoo boy where do I start?
 

Two easy infinites; one but mashing B, the other by mashing A. Both involve the fact that her launcher automatically jump cancels on hit, and can repeat infinitely after the groundbounce. I should also mention that both her launcher and full autocombo are both -3 on block, but considering how much distance there is between her and the opponent, good luck punishing her.
 
Second, this...

Even with the projectile limiter mechanic she has, meterless 300 damage with no scaling is absurd. I did mention she has no damage scaling, yes?
 

This Rem also has some very questionable hitbox placement, but this move takes the cake; its huge, its super meaty, has ton of priority, is invincible on startup AND completely immune to Normals during the active frames for some odd reason. The only respite you got is the fact that its -9 on block AND drags you toward her, so at least its punishable? Still stupidly abuseable though.
 
All of her Specials, save for one, also drain power from P2 for some reason.
 
All of this was from 5 minutes of playtesting her, and this is only scratching the surface. I'm afraid of seeing what other problems this character has.

This Rem, hoo boy where do I start?
 

Two easy infinites; one but mashing B, the other by mashing A. Both involve the fact that her launcher automatically jump cancels on hit, and can repeat infinitely after the groundbounce. I should also mention that both her launcher and full autocombo are both -3 on block, but considering how much distance there is between her and the opponent, good luck punishing her.
 
Second, this...

Even with the projectile limiter mechanic she has, meterless 300 damage with no scaling is absurd. I did mention she has no damage scaling, yes?
 

This Rem also has some very questionable hitbox placement, but this move takes the cake; its huge, its super meaty, has ton of priority, is invincible on startup AND completely immune to Normals during the active frames for some odd reason. The only respite you got is the fact that its -9 on block AND drags you toward her, so at least its punishable? Still stupidly abuseable though.
 
All of her Specials, save for one, also drain power from P2 for some reason.
 
All of this was from 5 minutes of playtesting her, and this is only scratching the surface. I'm afraid of seeing what other problems this character has.

This Rem, hoo boy where do I start?
 

Two easy infinites; one but mashing B, the other by mashing A. Both involve the fact that her launcher automatically jump cancels on hit, and can repeat infinitely after the groundbounce. I should also mention that both her launcher and full autocombo are both -3 on block, but considering how much distance there is between her and the opponent, good luck punishing her.
 
Second, this...

Even with the projectile limiter mechanic she has, meterless 300 damage with no scaling is absurd. I did mention she has no damage scaling, yes?
 

This Rem also has some very questionable hitbox placement, but this move takes the cake; its huge, its super meaty, has ton of priority, is invincible on startup AND completely immune to Normals during the active frames for some odd reason. The only respite you got is the fact that its -9 on block AND drags you toward her, so at least its punishable? Still stupidly abuseable though.
 
All of her Specials, save for one, also drain power from P2 for some reason.
 
All of this was from 5 minutes of playtesting her, and this is only scratching the surface. I'm afraid of seeing what other problems this character has.

This Rem, hoo boy where do I start?
 

Two easy infinites; one but mashing B, the other by mashing A. Both involve the fact that her launcher automatically jump cancels on hit, and can repeat infinitely after the groundbounce. I should also mention that both her launcher and full autocombo are both -3 on block, but considering how much distance there is between her and the opponent, good luck punishing her.
 
Second, this...

Even with the projectile limiter mechanic she has, meterless 300 damage with no scaling is absurd. I did mention she has no damage scaling, yes?
 

This Rem also has some very questionable hitbox placement, but this move takes the cake; its huge, its super meaty, has ton of priority, is invincible on startup AND completely immune to Normals during the active frames for some odd reason. The only respite you got is the fact that its -9 on block AND drags you toward her, so at least its punishable? Still stupidly abuseable though.
 
All of her Specials, save for one, also drain power from P2 for some reason.
 
All of this was from 5 minutes of playtesting her, and this is only scratching the surface. I'm afraid of seeing what other problems this character has.

Koishi updated
 
Adjustments to dash behaviors. Fix to guard behaviors regarding crossups. Adjustments to invincibility on Guard Cancel. Adjustments to reset behaviors. 6z: Damage decreased (80->70), Power gains decreased (120/60->90/45). 4z: Damage decreased (90->80), Power gains decreased (120/60->90/45). j5x: Damage decreased (50->40). j5y: Damage decreased (65->55). j6z: Damage decreased (90->80), Power gains decreased (120/60->90/45). j2z: Damage decreased (90->80), Power gains decreased (120/60->90/45). Catch & Rose: Damage decreased (111->101), Y & Z versions now properly deal chip damage. "Superego": Startup decreased by 8f, corrected persistent sound effect when Koishi is interrupted.

So its been almost 6 months since the last post here and there's a been a number of changes to the gameplay system, especially now that we have an actual playable demo of the system in the form of IZ Yukari, which was released last month. I suggest taking a look there for the most up to date changes to the system compared to what's listed here.
 
I kinda of want to steer the direction of this toward the next three characters planned for this system: Marisa, Sakuya, and Reimu. While these three won't receive that many drastic changes as Yukari did (it was mostly a last-minute decision due to her being included in 15.5, which was released in December), I do feel that I should go over some of the changes they'll be receiving, as well as any ideas anyone else has in mind.

Workaround for Missing "ParentExist" Trigger
Compatibility:
WinMUGEN Mugen 1.0 Mugen 1.1b IKEMEN  
 
Have you ever had a situation where you needed to create a complex projectile or effect that utilized a single helper creating multiple helpers that were bound to it, only to encounter a glitch where, in the event that the parent helper was destroyed, the child helpers would just sorta stay on screen and Mugen's debug is spitting out complaints that all your child helper's bindtoparent controllers have no parent to bind to. You rush to alter your child helper's Destroyself controller, only to realize that there is no "ParentExist" trigger you can use to force them to destroy themselves. Sounds like all hope is lost right? Fortunately there is a clever workaround using trigger redirection.
 
For each parent helper, you'll need to reserve one variable for a unique ID, while each child helper will require two variables; one to keep track of the parent's unique ID, and one to keep track of the parent helper's playerID, which is created by the engine each time a helper is created and are periodically recycled as helpers are destroyed and new helpers created to take their place.
 
In the first state of parent helper, at the following line of code to the beginning of its state:
[State 20000, Parent ID] type = varset trigger1 = time = 0 var(0) = random*1000+random
This will generate a unique, 8-digit ID when the parent helper is created. You only have to set this once each time the helper is created, even if the helper goes through multiple states. Note that there is a very small chance (approx 0.0001%) that the same ID will be created twice, but the chance is so miniscule that this will rarely, if ever, happen. That's all for the parent helper.
 
The child helper is where things start to get a bit complicated, so I'll go through each part here. In the first state the child helper is created in, add the following to the beginning of the state:
[State 20010, Parent Destruct Safeguard] type = varset trigger1 = time = 0 var(1) = parent,id ;Set to parent's PlayerID [State 20010, Parent Destruct Safeguard] type = varset trigger1 = time = 0 trigger1 = playeridexist(var(1)) var(0) = playerid(var(1)),var(0)  
What you are basically doing is copying the values of both the parent helper's playerID (which is set by the engine) and the 8-digit ID that you generated earlier, into the child helper. The reason for copying both of these values into the child helper is to check for two possible scenarios:
 
Scenario 1: Parent no longer exists, Helper with Parent's Player ID doesn't exist Scenario 2: Helper with Parent's Player ID exists, but unique ID don't match  
Scenario 1 is pretty straightforward; if a helper with the parent helper's PlayerID doesn't exist, then that means that the parent helper doesn't exist and you can safely destroy the child helper.
 
Scenario 2 is a bit more complicated to understand, and requires a bit of understanding of how the MUGEN engine assigns PlayerIDs. As stated before, PlayerIDs are recycled by the engine each time a helper is destroyed; MUGEN will typically use the first available free PlayerID in these cases. In other words, you may run into situations where a helper with the parent's PlayerID exists, but the helper with that ID was actually created after the actual parent helper destroyed itself! It is for this reason that we needed that unique 8-digit ID number, as PlayerID alone is not enough to check if the parent helper no longer exists.
 
To satisfy both of these scenarios when checking to see if a child helper's parent exists, your triggers should typically look something like this:
 
trigger1 = !playeridexist(var(1)) trigger2 = playeridexist(var(1)) trigger2 = playerid(var(1)),var(0) != var(0)  
Trigger1 will satisfy the first scenario; because there is no helper that exists with the parent helper's PlayerID, we can safely say that the parent was destroyed.
Both Trigger2s satisfy the second scenario; a helper exists with the same PlayerID as our child helper's parent, but their unique 8-digit ID number does not match what we initially recorded, indicating that the original parent helper was destroyed.
 
If you want to prevent any unusual debug errors, you should also add the following triggers to all State Controllers utilizing a parent that isn't the root (ie ParentVarSet, BindToParent, etc.):
 
triggerall = playeridexist(var(1)) triggerall = playerid(var(1)),var(0) = var(0)  
These triggers will check for the same consistency as the ones we defined above. If everything checks out, then the state controllers will execute without any problems. Otherwise, the controllers will not execute and prevent unnecessary debug flood.

Yukari Yakumo (Incident Zero style) released (03/22/18)

 
A new version of the youkai of boundaries, Yukari, has been released, this time with a new gameplay style to serve as a demonstration of the upcoming fullgame project, "Touhou: Incident Zero". This version can be found in the new "Incident Zero style" section of the character downloads.
 
Link: http://ricepigeon.neocities.org
 
First release.

Reminder regarding blacklisted websites
While Mugen Free For All strives to provide a warehouse directory for all M.U.G.E.N content made throughout the engine's existence, various creators across the world may choose to adopt different methods of hosting. While many of these sites are safe, some are not. Over the past few months, we've noticed a growing number of such sites, which we have had to remove. Either due to ethical/moral concerns over monetizing free content, or due to security exploits, we have had to blacklist these websites. We ask that you do not link to any of these blacklisted websites, as these links will be deleted on sight and the person responsible will be infracted, with repeat violations warranting further disciplinary action if necessary. If you notice any of these links, we ask you to please use the report to staff function so that we may address them accordingly.
 
The following websites/urls have been blacklisted due to known security vulnerabilities and/or unethical practices:
2shared Adb.ug Adf.ly Cashfly Ceestyy.com Coinurl Destyy.com Easyurl.net Festyy.com Gestyy.com Link4ad.com Linkbucks Mugenarchive Sh.st Shortenurl.tk Shorte.st Urlcash as well as any website listed here  
The following websites/urls, while not blacklisted, are discouraged due to requiring user registration:
4shared  

Suika Ibuki released (12/25/17)

 
The drunken oni of Gensokyo, Suika, has been released.
 
Link: http://ricepigeon.neocities.org
 
 
First Release

Suika Ibuki released (12/25/17)

 
The drunken oni of Gensokyo, Suika, has been released.
 
Link: http://ricepigeon.neocities.org
 
 
First Release

Suika Ibuki released (12/25/17)

 
The drunken oni of Gensokyo, Suika, has been released.
 
Link: http://ricepigeon.neocities.org
 
 
First Release

Reminder regarding blacklisted websites
While Mugen Free For All strives to provide a warehouse directory for all M.U.G.E.N content made throughout the engine's existence, various creators across the world may choose to adopt different methods of hosting. While many of these sites are safe, some are not. Over the past few months, we've noticed a growing number of such sites, which we have had to remove. Either due to ethical/moral concerns over monetizing free content, or due to security exploits, we have had to blacklist these websites. We ask that you do not link to any of these blacklisted websites, as these links will be deleted on sight and the person responsible will be infracted, with repeat violations warranting further disciplinary action if necessary. If you notice any of these links, we ask you to please use the report to staff function so that we may address them accordingly.
 
The following websites/urls have been blacklisted due to known security vulnerabilities and/or unethical practices:
2shared Adb.ug Adf.ly Cashfly Ceestyy.com Coinurl Destyy.com Easyurl.net Festyy.com Gestyy.com Link4ad.com Linkbucks Mugenarchive Sh.st Shortenurl.tk Shorte.st Urlcash as well as any website listed here  
The following websites/urls, while not blacklisted, are discouraged due to requiring user registration:
4shared  

Mokou updated
 
Increased vertical hurtbox size on forward dash. 5z: Damage decreased (85->75). 6z: Damage decreased (46*60->41*55). j5z: Damage decreased (95->90). j2z: Damage decreased (100->90). Hollow Giant Woo [1st Hit]: Damage decreased (50/55/60->45/50/55). Hollow Giant Woo [2nd Hit]: Damage decreased (50/55/60->45/50/55). Ignition Candle: Proration decreased (85%->75%). Mt. Fuji Eruption: Damage decreased (90->75), Proration decreased (80%->75%). "Immortality's Reckless Sacrifice": Fixed graphical bug in IKEMEN.

Chen updated
 
"Soaring Bishamonten": Fixed conflicting code that rendered Chen vulnerable after 1st hit. "Soaring Bishamonten": Added safeguard in case opponent gets stuck in hitstate.

Reminder regarding blacklisted websites
While Mugen Free For All strives to provide a warehouse directory for all M.U.G.E.N content made throughout the engine's existence, various creators across the world may choose to adopt different methods of hosting. While many of these sites are safe, some are not. Over the past few months, we've noticed a growing number of such sites, which we have had to remove. Either due to ethical/moral concerns over monetizing free content, or due to security exploits, we have had to blacklist these websites. We ask that you do not link to any of these blacklisted websites, as these links will be deleted on sight and the person responsible will be infracted, with repeat violations warranting further disciplinary action if necessary. If you notice any of these links, we ask you to please use the report to staff function so that we may address them accordingly.
 
The following websites/urls have been blacklisted due to known security vulnerabilities and/or unethical practices:
2shared Adb.ug Adf.ly Cashfly Ceestyy.com Coinurl Destyy.com Easyurl.net Festyy.com Gestyy.com Link4ad.com Linkbucks Mugenarchive Sh.st Shortenurl.tk Shorte.st Urlcash as well as any website listed here  
The following websites/urls, while not blacklisted, are discouraged due to requiring user registration:
4shared