User talk:TheFarix

If you want to change a thing on lots of pages at once, admins can use a ReplaceText function; just request for me to do it and I'll do it for you.

Thanks for the notice. Didn't know that text replace function existed. It could have saved a lot of work as I was so wishing I could use the AWB here. =\ There are still 80 pages that need the deprecated DropList replaced with ObtainList. You can find them in Needs Updating.

Why did you give Ranged Weapons its own list templates? If it was something difficult like Cylinders I'd understand but you can do Ranged Weapons much more easily.

Plus, Range already was in the List template... It auto-detects if the Range Parameter exists. If it does, it shows it under Hit Count and Speed.

Speculation from a GM=News

Actually, no. Speculation is speculation, and it doesn't belong on the front page.

It's still news, deal with it.

Speculation is never news, even if it is form a Nexon Staff member. There have been plenty of times Sabina speculation about when various issues being fixed or released, but end up being wrong. News announcements should be based on official announcements from Nexon.

First of all, that's your opinion. I don't recall that being a rule. Stop this revision war please, this is still news worth and it even says that it is speculation.

Speculation is never news. And if you want to stop the revision war, then you are free to walk way.

If you really feel strongly about this bring it up to Angevon or Ikkisuki and we might be able to make a policy concerning this, but at the minute, there is no rule for this so your removal is no different from vandalism.

I'd also like to point out that speculation is often news, you obviously don't watch the news.

Ehh if you ask me, if it came from a community manager like Sabina, or a GM, it's usually of great importance since:

• A) They probably got the info from the head developers
• B) They work for Nexon, so information is usually circulated.

x.x though it is usually speculation, sometimes it is true, and sometimes it is not. Circumstances change, but players have the right to know what's going on in the forums through tidbits of information since they either never surf the forums, or hardly use external sites to gather information other than this wiki.

Guys just wondering, how do you guys know if a maintenance is extended by hours? And if so how can I have the ability to know the extent of a maintenance?

Just check the maintenance's page like we do. O .o They should have an amendment at the top of the page.

Matanance was suppose to end at 12pm PDT. Then, at around 11:30pm, Nexon announced that it has been extended to 2pm PDT. It's not hard to do the math to see that it is a 2 hour extension.

I for one would still prefer information on Nekojima, even if it will never reach NA. And have known others to also use that page for information. You really shouldn't mark a controversial subject up for deletion without discussing it.

All of the FMA pages were deleted because they were never going to be released in NA. So why keep other pages on things that will never be released in NA? There should be consistantancey here.

Why were the FMA pages removed? They never said it will never reach NA... And I disagree, keeping information > condensing information.

Angevon deleted the entire set back in January on the bases that they will never going to be implemented. I don't see why Nikojima would be an exception to that rational.

I don't see why FMA stuff applied either... Doesn't mean we'll never get it. Korea even got them a year late.

They had to get the license for the stuff to be published. Look at AnoHana for JP Mabi (Second mabi-lized anime). It took them a while to get the license to publish the items. I think a fraction of profits went towards the creator or something. In any case, we're gonna have to wait until Nexon NA gets the okay.

Exactly as Lexis said, that being said, nobody can say "they were never going to be released in NA" until NA, DevCAT, or the creators say so. Either way, I don't think we can compare the removal of clothing we will never get with the removal of places we will never get.

Just FYI... the FMA stuff is translated in the game-files.

How are you getting them?... Some of the items aren't out yet.

They are coming directly form the client's DDS files. It's just a matter of matching the correct image with the correct item, which prowling through itemdb.xml helps with.

Yes, but the crafting images=/=the dds files, they are different shades of gray...

That's because the contrast has to be adjusted.

The easiest way is to have someone drop the item, you right click it, and have them pick it up while the window is still up. That's how I take the images. It is exactly the same as the "crafting in progress" image.

Oh, thanks. I'll try that when I come across a missing image.

I try to replace them but always slips my mind @@ plus some items are harder to come by...

While they not an exact, they are only one to 5 points off and no one is really going to notice the difference. So don't fret too much if you can't find a particular scroll for an image.

o.o must be my screen then...the both look the same to me xD;; :x but as long as something is there, I can't complain.

I was referring to the images from the DDS files and the images as they appear in game.

Looking at some of the images on the tailoring list, such as the Traveler Outfits and the Clover Pick Costumes, I'm beginning to think that many of the images are regular inventory icons converted to grayscale. At which point, they will not be close to an accurate representation of the in-progress image.

My apologies, I was looking at the 105_to_106 files and it said Monk everywhere in there. I'll ask NxBoo or Sabina and get to the bottom of it.

Thread:Talk:Wiki Home/Food Template
Example of what it does.

Fixed

Also, about the Shadow Monster template:

“	Um why is there no edit/link button next to these bandits?	„
—Infodude575

That one I don't understand as I just check Template:StyleShadowMonster and the edit and anchor links are there.

Where did you get the data of when what production feature was released when? Because I kind of remember there being an update releasing Handicrafting and kits, which would been its not from Beta, but I'm probably wrong.

The data came from the production.xml file, which lists Generation and Season the item was introduced. Some of these, like the event only items, are clearly wrong. But tracking down other mistakes will be difficult at best.

I'm still trying to figure out what production data will ultimately be included in the data templates based on what data will be the most helpful to least helpful.

But why did you put the giant puppet sitting positions up for deletion without a reason on the page?

I didn't put it up for deletion. I put it up for a rename. For one, in accordance with image policy, file extensions should be in lower case.

“	Make all file extensions lower case (use .jpg not .JPG, for example). Upon upload you can edit the target filename to correct the extension.	„

Second, the naming standards for race and sex is <Race> <Sex>. For example Giant Male. The image you uploaded had the two reversed "Male Giant".

When I uploaded it, that's how it was set on the upload page. But alright.

1. ifexist is an expensive parser function cap, and there's a limit on how many times it can be used. If one exceeds the limit, the next #ifexist just breaks.

Ok, that explains why the last image on the test page was breaking. At first, I though it was a problem with the new template, then the image.

There wasn't a need to create them. Template:StyleItemEtc has an Icon parameter added in, you just had to put in "|Icon=Note" for the pages using the same icon.

Other than for Hicca's Note, the redirects already existed. I just simply fixed them to point to the correct image.

Ah...right. M'bad for missing the lack of "N"s, then.

May I ask what the purpose of Template:Ifempty? If it's for blank parameters, there is already a naturally working workaround for that, people just need to know the coding 'style.'

The documentation page should explain its purpose. But it's a much easier way then using multiple #if: statements for default values.

Pulling up multiple instances of the same template that uses the same if statement 9 times is much more workloading than a simple if statement. :l

The only difference is the overhead for a template call. But the workload is negligible and the avoids confusion than using nested if statements.