Suggestion to the Wiki's template magicians once the upgrade is over

[Milt]

Hello, this is Milt. You may have heard of me.

I'll cut to the chase: I personally believe the worldfound# parameters in the FishInfobox template should be phased out. My reasoning? I'll use the Be Mine Fish page as an example.

| worldfound1 = Avalon
| locationlist1 =
Caliburn;

| worldfound2 = Grizzleheim
| locationlist2 =
Northguard;

| worldfound3 = Krokotopia
| locationlist3 =
The Oasis;

| worldfound4 = MooShu
| locationlist4 =
Jade Palace;

| worldfound5 = Wizard City
| locationlist5 =
Garden of Hesperides;
The Commons;

| worldfound6 = Zafaria
| locationlist6 =
Baobab Crossroads;

| worldfound7 = 
| locationlist7 =

All this code can be condensed down to a single list:

| locationlist =
Baobab Crossroads;
Caliburn;
Garden of Hesperides;
Jade Palace;'
Northguard;
The Commons;
The Oasis;

Not only does the end result look much cleaner and potentially less intimidating for contributors to edit, it would also cut down on the amount of space each fish page takes up in the W101C Wiki's servers by quite a healthy margin.

I'm certain the Wiki's codebase is capable of inferring a location's world on its own. It could split the singular locationlist array into many smaller arrays differentiated by world. A potential problem I can see with this approach though is that it may be inefficient.

Well? What if the Wiki assigns a number to each location? Each number could be assigned based on the location's name, the location's position in an alphabetical list of locations of its origin world, and its origin world's position in an alphabetical list of worlds!

Here are all the worlds currently in the game in alphabetical order: Arcanum, Avalon, Azteca, Celestia, Dragonspyre, Empyrea, Grizzleheim, Karamelle, Khrysalis, Krokotopia, Lemuria, Marleybone, Mirage, MooShu, Novus, Polaris, Wizard City, Wysteria, and Zafaria. That's 19 worlds in total.

And now for the fun part: let's allocate blocks of numbers to each world. Each block would contain 1000 numbers - the number has to be huge to account for all those locations and sublocations in each world. Arcanum would be given numbers 1000 to 1999, Avalon would be given numbers 2000 to 2999, Azteca would be given numbers 3000 to 3999, and so on until Zafaria (19000 to 19999). As stated earlier, all the world's locations and sublocation's would be given numbers strictly within their world's allocated range.

The first number in a block should always be given to the world itself (e.g. Arcanum is 1000). This is to ensure that the Wiki can safely assume that numbers 1001 through 1999 are either locations or sublocations.

Now let's give Arbiter's Arena a number of 1001. How can the Wiki use this number to determine that the Arbiter's Arena is found within the Arcanum? Simple, take the number (1001) and round it down the next lowest thousand, which happens to be... well, 1000. What location has 1000 as its number? Why none other than the Arcanum, of course! See? Simple!

I don't think the numbers themselves need to be assigned manually either. An array could be set up to keep a running census on every world, location, and sublocation in the game, ordered alphabetically. And the Wiki should be able to generate ID numbers for each item in the master array automatically. Maybe such an array already exists?

[Marcus StrongThief]

Hello, this is Milt. You may have heard of me.

I'll cut to the chase: I personally believe the worldfound# parameters in the FishInfobox template should be phased out. My reasoning? I'll use the Be Mine Fish page as an example.

| worldfound1 = Avalon
| locationlist1 =
Caliburn;

| worldfound2 = Grizzleheim
| locationlist2 =
Northguard;

| worldfound3 = Krokotopia
| locationlist3 =
The Oasis;

| worldfound4 = MooShu
| locationlist4 =
Jade Palace;

| worldfound5 = Wizard City
| locationlist5 =
Garden of Hesperides;
The Commons;

| worldfound6 = Zafaria
| locationlist6 =
Baobab Crossroads;

| worldfound7 = 
| locationlist7 =

All this code can be condensed down to a single list:

| locationlist =
Baobab Crossroads;
Caliburn;
Garden of Hesperides;
Jade Palace;'
Northguard;
The Commons;
The Oasis;

Not only does the end result look much cleaner and potentially less intimidating for contributors to edit, it would also cut down on the amount of space each fish page takes up in the W101C Wiki's servers by quite a healthy margin.

Excellent idea, but I believe we're a step ahead of you right now.

The idea is to eventually remove those fields entirely and have the page find the world and locations automatically. Our current direction is to be moving all location and world related information onto location pages themselves so that we may deprecate location fields on most other templates. CastleInfobox and the new LocationInfobox (in conjunction with the new WorldInfobox) should make this possible. However, rolling out the new version of LocationInfobox has proved time-consuming, so only Polaris and Krokotopia have been completed. We haven't really advertised this project because well... we weren't expecting it to take this long.

This project has also fallen at the wayside at the moment due to the site upgrade that is currently taking place. If you are interested in it though, feel free to reach out to me as we would love more hands working on it.

[Milt]

Excellent idea, but I believe we're a step ahead of you right now.

The idea is to eventually remove those fields entirely and have the page find the world and locations automatically. Our current direction is to be moving all location and world related information onto location pages themselves so that we may deprecate location fields on most other templates. CastleInfobox and the new LocationInfobox (in conjunction with the new WorldInfobox) should make this possible. However, rolling out the new version of LocationInfobox has proved time-consuming, so only Polaris and Krokotopia have been completed. We haven't really advertised this project because well... we weren't expecting it to take this long.

This project has also fallen at the wayside at the moment due to the site upgrade that is currently taking place. If you are interested in it though, feel free to reach out to me as we would love more hands working on it.

Interesting! Feel free to contact me with additional information about this project. I reckon the team is looking for volunteers to jump into the trenches and perform template conversions?