Talk:Community Portal

From Ring of Brodgar
Jump to: navigation, search

Use this page for discussion of current and future RoB Projects

Legacy naming standard

Thinking about a general standard to be used for naming Legacy stuff.

For the default Legacy subject pages this is taken care of by the Legacy name-space.
But for other page types, like images, properties, etc this is not available. (at least not currently)

Using a leading, but fake, name-space looking "Legacy:*" part is probably not such a good idea.

Next best thing seems to be to use a leading "Legacy_*" name part. which seems ok/best (at this moment).
One potential issue with the leading "Legacy_*" part (compared to using a trailing one) is that mediawiki is only case-insensitive for the first character of a page name.
ie: for real ns "Legacy:Loom" == "legacy:loom", but for a fake ns like with "Property:Legacy:Hurt" == "property:legacy:Hurt", but <> "Property:Legacy:hurt" (as "Legacy:Hurt" in this case is the actual page name)

The trailing variant is not free of potential issues either, as you (probably) can't search for stuff that begin with "Legacy". And no nice grouping of Legacy stuff when viewing alphabetical sorted lists of course.

Any comments? Other ideas? or Pro's or Con's I might have missed?
--.MvGulik. 20:32, 25 November 2017 (EST)


I dont see any problem with "File:Legacy_*" or "File:Legacy-*". You've probably noticed that some files here are named "File:Hafen-*". I personally feel having the main wiki files be named "file:*" is better than "File:Hafen-*". There might be some capitalization issues, but that can be worked around easily.

I'm not certain how, but you may be able to make a "Legacy File" or "LegFile" namespace to hold all necessary legacy images and properties. that may be something worth looking into --Ricky (talk) 00:36, 26 November 2017 (EST)


"Legacy_*" versus "Legacy-*":
I did not think about that one. Using "-" instead of "_" might not be a bad idea. I see one potential/conditional pro. Not sure yet about potential con's.

"Hafen-* versus "Legacy-*":
Yea, there is no real need to use "Hafen-* for the current-game/main subjects or other stuff, presuming Legacy stuff being completely separated. For page-icon related images that is currently a bit of a problem though (including potentially maintaining and splitting there wiki history).

New Namespaces:
Only Mediawiki Bureaucrats (ie: Spiff) can create new namespaces. So separate Legacy namespaces for Files, Properties, etc. are currently out. On top of that, I don't know how long the Legacy game will be kept on-line. But at some point I figure it will be taken down. (actually I'm a bit amazed its still around)

--.MvGulik. 06:04, 26 November 2017 (EST)


Going with '-' separator for both "Legacy-*" and "Hafen-*" (img-only). Adds a bit more work, but its good practice. --.MvGulik. 04:06, 27 December 2017 (EST)
--- Update existing "Legacy_*" to "Legacy-*": Done. --.MvGulik. 06:46, 27 December 2017 (EST)

Page related icon image names (Hafen v Legacy)

After giving it some more thought I came up with the following for separating Hafen and Legacy images.

1) Until the separation is complete. Using "Hafen-{PageName}.png" as default for hafen page related icon images.
- After the separation is complete, a global replace could be used to change or ditch the image "Hafen-" part.

2) Moving image pages, with Legacy only images, to "Legacy_{PageName}.png" (without leaving a redirect)
- Will look into some image check in the MetaObject template to switch to available image versions ("{pagename},png", "Hafen-*" or if those fails "Legacy_*")
- Some similar thing for the Legacy-MetaObject template.
- Needs some way to direct the user, on main:pages, to the "Hafen-*" image for image updating.

3) Image pages with mixed Legacy and Hafen images. ... Leave as is for now.
- (I need to experiment a bit with history splitting first)
- Other: Will look if its possible to creating a temporary "Legacy_*" image directly from RoB wiki, ie: without download+re-upload.
- PS: Ricky. I think its best if I'm going to be the only one doing this history manipulation on active RoB wiki pages for the time being. When I build up some experience and got a good overview on it, I could write some documentation if needed.

--.MvGulik. 14:48, 27 November 2017 (EST)


Sounds good, boss. Just holler if you need anything. --Ricky (talk) 16:37, 27 November 2017 (EST)

Localized Resources

I think its about time we rebuild the Localized Resources page. Each of the localized resources and their materials should have their own page.

  • each resource should have a picture of what the resource looks like when active/depleted (in full light)
  • each resource needs # of materials each node holds, as well as average respawning time
  • each resource needs its skillcap (i think we already have this)
  • each resource needs its terrrain/location (I believe some are universal, such as heartwood, but ice spires, guano, etc. need this info)
  • each resource should display its experience event

Basically everything the Localized Resources page displays should be on each individual page


Are you thinking "Localized Resource" template ? (as that popped-up in my mind)

Just in case. CSV dump of "localized resource" table data.

"-- NODE --","-- NODE --",,,"-- Resource --","-- Resource --",,,
"IMAGE1 (File:***.jpg)",Text,Biomes,XP,"IMAGE2 - Icon (File:***.png)",Text,"Quality Cap",Decays?,Use
Abyssal_Chasm,"Abyssal Chasm","[[Mountain]], [[Cave]]",400,Hafen-Foul_Smoke,"[[Foul Smoke]]",Stealth,<?>,"Curio Q10:(LP = 10000, weight = 20, expdrain = 60, studytime = ?)"
Ancient_Windthrow,"Ancient Windthrow",Forest,400,Hafen-Ancient_Root,"[[Ancient Root]]",Survival,Yes,"Heals HHP equal to its quality, evenly spread over all wounds."
Clay_Pit,"Clay Pit",<empty>,400,Pit_Clay,"[[Clay|Pit Clay]]",Masonry,No,"[[Paving#Pavement Styles|Blue brick paving]], possibly porcelain."
Geyser,[[Geyser]],"Mountain (snow), Grassland, Dryflat, Mountain (red), [[Cave]]",400,Hafen-Brimstone,[[Brimstone]],Survival,Yes,"Can be used to make [[Catapult]] and [[Matches]]"
Cave_Organ,"Great Cave Organ",[[Cave]],400,Notes_of_a_Foul_Symphony,"[[Notes of a Foul Symphony]]",Stealth,<?>,"Curio Q10:(LP = 3000, weight = 12, expdrain = 30, studytime = ?)"
Guano_Pile,"Guano Pile",[[Cave]],400,Hafen-Bat_Guano,"[[Bat Guano]]",Farming,<?>,"Can be used to fill [[Treeplanter's Pot]], replacing [[Soil]]. Guano is generally of a higher quality than soil."
Headwaters,Headwaters,[[Mountain]],400,Hafen-Water,"[[Spring Water]]",Survival,No,"Similar to water, can get better results if used for tree planting (needs testing) (+10 sta -18 e, 0.05 L/sip at q20)."
Heart_of_the_Woods,"Heart of the Woods",Forest,400,Hafen-Heartwood_Leaves,"[[Heartwood Leaves]]",Survival,No,"Restores [[Travel Weariness]]. Can be [[Equipment Gilding|gilded]]."
Ice_Spire,"Ice Spire","[[Mountain]] (snow-covered part)",400,Hafen-Ageless_Ice,"[[Ageless Ice]]",<empty>,<?>,"Instantly finish all curios in study."
Jotun_Mussel,"Jotun Mussel",Lake,400,Hafen-Mother_of_Pearl,"[[Mother of Pearl]]",Exploration,<?>,"Curio (LP = 8000, weight = 15, expdrain = 10, studytime = ~75m), ..."
Crystal_Rock,"Rock Crystal","[[Mountain]], [[Cave]]",500,Hafen-Rock_Crystal,"[[Rock Crystal]]",Smithing,No,"Curio (LP = 2500, weight = 4, expdrain = 40, studytime = ?), ingredient in [[Charter Stone]]s and [[Realm]]s. Can be [[Equipment Gilding|gilded]]. Stone axe or pickaxe required to collect"
Salt_basin,"Salt Basin",<empty>,400,Hafen-Salt_Crystal,"[[Salt Crystal]]",Cooking,No,"Decrease hunger level by 20% at q10."

--.MvGulik. 14:14, 19 December 2017 (EST)


Sounds great, make an example with any resource - even with missing information, and i will try to finish others.

Also current table should be exist, updated to category ofc and hold all this information in one place.

--Kitsuneg (talk) 15:12, 19 December 2017 (EST)


Okay, I filled in Abyssal Chasm with all the information i think is important for each page. if there's anything i'm missing, just add it.

Wasn't sure about making a new template for ~15 objects, so I just make a "template" to be manually filled in.
I didnt want to bother making a new template interact with the infobox, so I think this will suffice.
Kitsune, if you want to change the wording or anything about the template I made, feel free to do so.
Its better to do any fixes now to the first page before you copy it to the rest of the pages. I've been there and done that, it sucks ass

if you have any questions, just holler --Ricky (talk) 17:15, 22 December 2017 (EST)

Category:Containers

Added properties Xinv, Yinv, and Vinv to define storage containers. works exactly like Xsize and Ysize.
using Xinv will automatically add that page to Category:Containers, so we dont have to do that manually any more.
should look like this in the infobox:

|xinv = 5
|yinv = 5

I updated all the pages currently in the Containers category, but i think there's a bunch more stuff that's been missed, like the Saddlebag, Wagon, etc..
hopefully someone will add it in eventually.

--Ricky (talk) 16:45, 22 December 2017 (EST)

"Specific" property

Implemented the "Specific" property as "Infobox metaobj‎‎" template parameter.
Updated "Salad Greens‎‎" and "Any Mushroom" related pages. (as test and example cases)
All seems to work ok. If you see anything odd in relation to this update, report it at the Specific property talk page.
--.MvGulik. 16:46, 13 March 2018 (EDT)


Looking at the Cloth page, and seeing the kinda large 'Required By' objects list, there is one thought that keeps nagging me: "Can all those items be made with 'any' of the specified Cloth-types". The key word here is 'any'. If for example some of those 'Required By' objects can only be made by 3 or 4 of those 6 Cloth-types ... I'm not sure if they should be in that list. (probably a potential can of worms, but still something I kinda wonder about)
Currently is just a nagging though, on which 'I' have not done any further pondered or investigating (which will have to wait in my case, until I'm done with the Legacy related stuff that's on my todo-list).
--.MvGulik. 13:46, 14 May 2018 (EDT)


They can be made with any cloth, i did not check all that list, but mostly items where should be specific cloth - required it right.
Also goal for you future todo-list - we need "Specific" property - that can list 2 or more types, mohair yarn\cloth for exaple works as wool equivalent in recipes.
--.KitsuneG. 14 May 2018 (EDT)


Those req pages can get bulky, but there are few, if any, exceptions like what you're mentioning. Generally all of an item category (any cloth) or one specific type are used in a recipe. The closest example i can think of any mushroom vs edible mushroom. but even in these circumstances the devs prefer to make a new item category instead of specifying X, Y, or ,Z crafting item
--Ricky (talk) 15:04, 14 May 2018 (EDT)


Roger. --.MvGulik. 01:33, 16 May 2018 (EDT)
>we need "Specific" property - that can list 2 or more types
Added. Give it a try I would say. (ditched the category part for the moment). --.MvGulik. 23:12, 18 May 2018 (EDT)
What format/syntax should we be using? In the case of Red Deer Antlers, they should be both finebone and bone material. I tried a few formats, but none of them seem to be working for me.
--Ricky (talk) 00:17, 19 May 2018 (EDT)
Try infobox parameter. ie: "| specific = finebone, bone material, etc". --.MvGulik. 05:05, 19 May 2018 (EDT)


PS: It might not be a bad thing to look at potential naming-styles for those general(specifics) pages. --.MvGulik. 07:16, 19 May 2018 (EDT)

Legacy pages - changes

(Just for logging the major stuff)

  • Disabled skills-infobox output for "Skill(s) Enabled" and "Required By" parts.
  • Forced all page-links to link to Legacy namespace. (which broke some links of course, to be fixed later)
    • Forced all page-links to use alternative link-text (to not show the "Legacy:" part).
  • ...

--.MvGulik. 13:45, 4 April 2018 (EDT)

File/Image naming

Changed the names of some files for the sake of image-naming clarity. For Barrels and Cheese Trays the scheme should be self explanatory. The (on wall) scheme should probably not trigger any problems either, ... the (wearing) scheme however (one case, as it needed to be moved out of the way) seems a bit troublesome. As characters are wearing more than one item at a time (ie: images are/can be used by different pages), and wearing a cigar or wearing a wielding sword sound not right to me. So on that part, character specific screenshot naming, some additional thinking is probably not a bad idea. --.MvGulik. 07:34, 22 April 2018 (EDT)


Moved/renamed the majority of '(single)object on wall' type images to "<related object-page-name> - (on wall).<ext>" (including updating the pages that used these images of course). --.MvGulik. 05:10, 28 April 2018 (EDT)
Changed/renamed any and all image/file extension's with caps to full lower-case extension. --.MvGulik. 13:15, 2 May 2018 (EDT)

Automated Game-Update processing

Recently I switch to an other code editor, which allows (ie: makes it easier) for more structured programming than the old one I was using.
To get accustomed to this new editor I focused on extending the automated RoB-page updating related to new game patch+hat updates.
If all works as intended (hidden bugs notwithstanding) the following things get done after a new patch is spotted. (manually initiated btw)

  • Uploading of new hat resource/icon image(s). (if not already exist)
  • Creation of initial new hat page(s) (if not already exist). (using the New store hat page template for this)
  • Updating the Store hat list with new (patch) hat(s), including updating dropped hat(s).
  • Updating the Game Updates page with a new patch/update row.

I hope the RoB users that usually took care of some of those parts don't feel bypassed by this automation.
--.MvGulik. 20:24, 12 June 2018 (EDT)

Troubleshooting and Instructions

  • Symptom: Changes in one section of the wiki not showing up in another section of the wiki.
  1. Hit Refresh at the top of each wiki page affected
  2. Edit/Save each wiki page affected. (You dont need to actually edit anything, just open/save the page
  3. Perform a Super Refresh of your browser by pressing: Windows:CTRL+F5, Mac/Apple:Apple+R, Linux:F5.

First: Well as my mate notice - if we follow that instructions, the page will dissapear from every related pages. Isn't just a Refresh button enough?

Second: We should somehow aware new editors about that, that information hard to find, i myself was needed Ricky instructions personally before i get it. Well we can mannualy write each new active editor about that, but its super annoying..

  • one suggestion - to put a reminder note here, but.. who actually would read this =(

Third: Maybe Ricky? should start new Wiki official thread on forum? with updating info on first page, instructions , etc..

--Kitsuneg (talk) 21 June 2018 (EDT)


>"Isn't just a Refresh button enough?"
Yes, that [refresh] button should do the trick to. (I never use it, as I'm to accustomed to the other way (its also not always precent on other wiki's.)) --.MvGulik. 14:19, 21 June 2018 (EDT)