FANDOM


  • The template is closed and also looks like a mess, I propose someone me or someone else should clean it up, mostly rearranging things. Kairos is also in Dragon Variable 1 while the other legendary dragons are in Dragon variable 2, confusing isnt it. If the an identical dragonbox kairos shows up twice, will it break the system?

      Loading editor
    • That template is for the dragons released prior to 2016. The dragons released after that are in second variable.

        Loading editor
    • Why though?

        Loading editor
    • There would have been too much data in one template. It was taking awhile to load when editing.

        Loading editor
    • It's funny you bring this up right now since yesterday I was just trying to set older holiday dragons like Holly and Gift as available right now and realized what a mess the whole system is atm. Perhaps setting dragons into template categories would make it easier to update their availability status. A template for epic, limited, and non-limited possibly?

      Possibly some other way of setting which limited dragons are currently available. Possibly a one-line toggle where you would just list the dragons available. Like: currently available=holly, gift, mistletoe, starshine

      All other limited dragons would default to EXPIRED if they're not on the list.

        Loading editor
    • So that toggle function would be like

      toggle inact (#) toggler show/hide var/inact # var # etc. Doesnt seem to difficult, though format integration could be a little tricky.

      Back to the dragon thing, I get what you mean, but we could either cap eah variable every 2 years, since the length of each variable seems about the same, but that doesnt really fix the problem rather ignores it. Or we could do what Mendo proposed and have access to all of them and divide based on "elements" /groupings

      For the toggle thing, wed probably create templates of dragon groups limited and permanet and then maybe have 2 toggle variables attached to the main dragons. Maybe? Bcuase at this point limited dragons have become a section all unto them selves. 

      Unrelated note can we all kind of agree that the older pages are outdated and fairly abandoned when it comes to updates, ex. Kairos, every asset of that whole topic is old and needs to be revised, which I am slowly woring on.

      In fact earlier today I was looking at the Perch of Kairos coding and it was messy and hard to read.

        Loading editor
    • OuroDragon
      OuroDragon removed this reply because:
      redundant
      02:55, December 17, 2018
      This reply has been removed
    • OuroDragon
      OuroDragon removed this reply because:
      redundant
      02:56, December 17, 2018
      This reply has been removed
    • OuroDragon
      OuroDragon removed this reply because:
      redundant
      02:56, December 17, 2018
      This reply has been removed
    • To change availability do you have to go into each and every dragon file and change it? if so, Theres gotta be a more efficient way of doing it

        Loading editor
    • OuroDragon wrote: To change availability do you have to go into each and every dragon file and change it? if so, Theres gotta be a more efficient way of doing it

      Yes currently you have to go to each one individually and change the value on the specific dragon value: limited = Expired

      Full example:

      | hiddenbolt = {{#switch: {{lc:{{{2}}}}}
        | disp_name = Hidden Bolt Dragon
        | desc = <center>Motto of the House of the Hidden Bolt: "Sparking Curiosity"</center><br>Look at that mischievous expression! The hidden bolt dragon is like the cat that swallowed the canary... if the canary were made of lightning, that is. It's easy to see where the mischief-makers of the House of the Hidden Bolt got their inspiration for impishness.
        | level     = 12
        | buy       = 220
        | sell      = 1,000,000
        | hatch     = 200,000
        | rate      = 500
        | element1  = Dark
        | element2  = Lightning
        | element3  = 
        | element4  = 
        | breeding  = 22 H 
        | upgraded  = 17 H 36 M
        | incubate  = 22 H
        | boostpos1 = Dark
        | boostpos2 = Lightning
        | boostpos3 = 
        | boostpos4 = 
        | boostneg1 = N/A
        | boostneg2 =
        | boostneg3 =
        | boostneg4 =
      |image        = [[File:HiddenBoltDragonAdult.png|x175px]]
      |juvenile     = [[File:HiddenBoltDragonJuvenile.png|x175px]]
      |baby         = [[File:HiddenBoltDragonBaby.png|x175px]]
      |egg          = [[File:HiddenBoltDragonEgg.png|x175px]]
      |imagetwin    = [[File:HiddenBoltDragonTwinAdult.png|x175px]]
      |juveniletwin = [[File:HiddenBoltDragonTwinJuvenile.png|x175px]]
      |babytwin     = [[File:HiddenBoltDragonTwinBaby.png|x175px]]
      |eggtwin      = [[File:HiddenBoltDragonTwinEgg.png|x175px]]
      |type         = Rare
      |limited      = Expired
      |countdown    = 
      |rarity       = Rare
        }}
      

      Also they all seem to have a section for 'twin' images which as far as I can tell are not used anywhere on the site, nor does it make sense what those images would be since twins look just like the regular dragon other than the orb.

        Loading editor
    • Delete that section if you can, the point of code is to be efficient and as easy to understand as possible, if something isn't necessary dont include it.

        Loading editor
    • OuroDragon wrote: Delete that section if you can, the point of code is to be efficient and as easy to understand as possible, if something isn't necessary dont include it.

      It's not just that dragon though, there's hundreds of entries with those already there. I'm not sure what their original purpose was.

        Loading editor
    • Everything is controllable through the second variable. There is no need to edit the first.

        Loading editor
    • Thanks for the assistance folks!

      Feel free to let me know if you have any additional questions OuroDragon!

        Loading editor
    • It's honestly not that difficult to change a dragon from expired to available - especially on a desktop. Simply use Ctrl + F and then type in the name of the dragon. It's time consuming but not difficult when there are a lot of dragons that have to be switched. The variables have been coded as such that you, as Awesome said, don't need to edit the first variable.

      It may need to be that we start a third dragon variable with all of the dragons they're releasing. Could there be a variable just for limited dragons? That seems to be the bulk of what is being released right now. Just a thought.

        Loading editor
    • Like you said it's very time consuming. Just seems like there could be a lot faster way of doing it, like a single line you would just put the ones currently available in, all others would default to expired.

      I'm totally willing to organize all the dragons into different templates. We could do epics, non-epic permanents and limited templates. Seems that would give us a lot of room to grow. Then you'd only have to edit the limited template. Perhaps a line at the top could be used to tell which ones are currently available.

        Loading editor
    • Im with Mendo on this, starting a new variable is to tacitly ignore the time consuming nature of the others. Will it still be time consuming? Yes, but r organizing the templates also opens up room for experimentation and change in efficiency. Tell you what, one of you guys who knows more about code than I do, create a sandbox and then when its done review it in this group chat and well reviese as needed, simple as.

        Loading editor
    • Also I think Karos has a total of 3 physical changes, pwr lvl 1-6 7-x and x-13. If its not already updated does anyone mind getting a HQ photo and forwarding it to me? It would be much appreciated.

      BTW Not just a minute ago I leveled Kairos to 7 woo! Milestone

        Loading editor
    • If we were to split templates up, I would just do limited and permanent. Too many variables would get confusing when setting up the actual dragon page. If we didn't want to split the variables, a line for coding kind of like what is in the second variable for limiteds might be the easiest method for changing expired/available.

        Loading editor
    • OuroDragon wrote:

      Also I think Karos has a total of 3 physical changes, pwr lvl 1-6 7-x and x-13. If its not already updated does anyone mind getting a HQ photo and forwarding it to me? It would be much appreciated.
      Kairos 12 to 13

      I don't see any difference in Kairos. I think his perch might have changed, but I didn't think to take a pic of the perch before I leveled him up.

        Loading editor
    • Interesting, 

        Loading editor
    • Kairos Level
        Loading editor
    • Is it a special thing possibly? Or is it fake?

        Loading editor
    • No you know whats wierd, in your personal world, the chronolith lights up, in a random parks world it doesnt...HOW??????????????O_o

        Loading editor
    • I thought he changed in appearance at certain levels too, but they were slight changes.

        Loading editor
    • So I may be mistaken, but is the suggestion to have a third variable where limited dragon status is changed there instead of scrolling through the dragon and decoration variables?

        Loading editor
    • I think so, we open the 2 variables and reorganzie them into limited and permantent. We could either list them by release date or by element (according to the elemnt breeder and dragonarium) and then by order of release as like an internal categorization. Same goes for the decoration variables.

      As an after thought what we could also do is cap the variables at a certain quantity and then start new ones, like what we have except named Limited 2 and Permanent 2 (not actual names, the names would be specific towards dragons and decor). So there would be little to no lag and the best of both worlds.

        Loading editor
    • So I split all the limited dragons off of both the DragonVariable templates into a locally stored text document, and it's quite large (9757 lines). I think we would need four templates altogether:

      • DragonVariable could be non-limited elemental dragons
      • DragonVariable2 could be the limited elemental dragons
      • EpicDragonVariable would be non-limited epics
      • EpicDragonVariable2 would be limited epics

      This would give room to grow and less lag on updating the files.

      I organized it alphabetically with epic element taking precedence.
      Non-epics are listed by Dragonarium category, with the first one they appear in alphabetically taking precedence.

        Loading editor
    • I would order limited dragons by release. It's easier to add to the end of the list than figure out where it goes in the middle.

      I don't think we need to split Epic and Elemental, just Permanent and Limited. With the hybrids of dragons that have both Epic elements and basic elements it will start to get confusing for some (not to mention Mythic and Legendary are technically not epic dragons). Depending on how long the game continues (it's been 7 years already and into the 8th) we're probably going to need to expand again anyways. Especially with limiteds as they keep releasing them over permanent dragons.

        Loading editor
    • Not to mention this variable layout needs to work with the decorations as well. Also the Dragonarium sortment of elemnts should have precedent over the element finder. Which would ean anything listed under epic is epic, and yes permanent and limited would be better.

      The list should go something like this

      Dragonarium Epic Chart





      or this

      Icon








      Or sort element sections by release of said elements.

        Loading editor
    • SO Im thinking

      Plant | Earth | Fire | Cold | Lightning | Water | Air | Metal | Light | Dark

      Order by release date of epics

      then Limited, so the limited epics and primary hybrids will be shorter than the limited dragons list

        Loading editor
    • Permanent Dragons 1 2

      Permanent Epic Dragons 1 2

      Limited Dragons 1 2

      Limited Epic Dragons 1 2

      Throwing out ideas

        Loading editor
    • CelticStar87 wrote: I would order limited dragons by release. It's easier to add to the end of the list than figure out where it goes in the middle.

      I don't think we need to split Epic and Elemental, just Permanent and Limited. With the hybrids of dragons that have both Epic elements and basic elements it will start to get confusing for some (not to mention Mythic and Legendary are technically not epic dragons). Depending on how long the game continues (it's been 7 years already and into the 8th) we're probably going to need to expand again anyways. Especially with limiteds as they keep releasing them over permanent dragons.

      Given the large about of limited dragons and that the majority of new dragons have been limited I would very strongly recommend making 4 templates for them.

      The sorting is not complicated, if a dragon has any epic element it would go into the epic template.
      Alphabetical makes more sense for organization and the Dragonarium can easily sort by Name alphabetically making it very easy. The text document I made has like the regular template form of organization but a bit clearer because it's sorted by Dragonarium categories. So like:

      <!-- BEGIN Rainbow Dragons -->
      
      Alphabetized list here
      
      <!-- END Rainbow Dragons -->
      
      <!-- BEGIN Seasonal Dragons -->
      
      Alphabetized list here
      
      <!-- END Seasonal Dragons -->
      

      Mythic/Legendary dragons are few and time is long between any new ones. So far none have been limited so I don't think that's something to be too worried about. I would just put them in with the epic list.

        Loading editor
    • I would also remove all the 'twin' image values from all of these entries. I can't find anywhere they are used at all on the wiki or that any have been uploaded or that they would have any use since twin dragons look exactly like normal dragons except for the border, bg and head bauble. I'd like for an admin to confirm that this value is not used anywhere though.

        Loading editor
    • Its not hard to sort by alphabetical, but do you really want to for every new dragon that comes out. It's a matter of efficiency vs. Looking more organized both of which will look good nut one of which will be faster and lazier. It depends on the priorities.

        Loading editor
    • Also where is this list?

        Loading editor
    • The reason I would go for release date is so it can be used as a reference point if you need to date certain areas and do quick math and ll that jazz, its easier knowing everything will be in order so yo're not toally lost on how the game has developed.

        Loading editor
    • OuroDragon wrote: The reason I would go for release date is so it can be used as a reference point if you need to date certain areas and do quick math and ll that jazz, its easier knowing everything will be in order so yo're not toally lost on how the game has developed.

      This is only for creating/updating dragonboxes, not for a list of dragons.

        Loading editor
    • We are taling about the variable right?

        Loading editor
    • The Dragonarium template may need some work. At the time of its creation there were less dragons and sections. The main concern is the amount of data in it which started to cause a "lag" upon the page loading after more releases.

        Loading editor
    • I think its because the code written for it was actually written into the paege itself and not a variable or template, I'll see what can be done

        Loading editor
    • I know when it was created each "section" and "sub-section" had its own template for easier list compilation.

      The amount of data was overwhelming which I think is why it was decided to "hide" the "All" template lists in each section.

        Loading editor
    • There are probably several templates/pages that need revamped/revised now since there is so more much content now compared to when they were created.

        Loading editor
    • A FANDOM user
        Loading editor
Give Kudos to this message
You've given this message Kudos!
See who gave Kudos to this message
Community content is available under CC-BY-SA unless otherwise noted.