User talk:Elembis

To "ping" me and direct my attention to a certain page, link to the page here: example

Thanks for helping clean up the wiki info. For the dollar values, gold coins were intentionally priced at $100 even though it wasn't the lowest common denominator -- I put more comments at the top of Talk:Trading. --Tycho44 03:04, 18 May 2006 (BST)

Shouldn't this be on his discussion page?--Wifey 06:05, 18 May 2006 (BST)

Ta-da. —unsigned by Lint 04:16, May 18, 2006 (BST)

Wups - Sorry about the mistaken edit. Thanks for creating the weapon breakage / dullage / critical hits / jungle-chopping XP gains page. --Tycho44 18:37, 21 May 2006 (BST)

Shark bites

*ping* On the Animals page you said that Shark bites persist, but this should probably be reported as one of the Bugs. On the Game Design page, the first section (Persistent Shark Bites), Simon claims that:

With the changes to the Shaman a couple of weeks ago, the shark bites are no longer persistent. --Simon 21:32, 8 May 2006 (BST)

—unsigned by Tycho44 07:48, May 22, 2006 (UTC)

Got it. I was going by information on Bugs#Not and didn't notice that a change had been made. Thanks! — Elembis 17:06, 22 May 2006 (BST)

Shaman redirects

Re: Shaman. Yeah, my thinking was redirecting the village shaman names to the shaman page since they aren't moving right now. However, I think it is beneficial to keep the wandering shaman articles listed individually so that chronological reports can easily be made and very geeky shaman tracking data can be extrapolated. --Lint 04:46, 23 May 2006 (BST)

You're right, tracking them over time would be interesting and probably insightful. How about redirecting their pages to Shaman and tracking them by commenting out previous date/time information each time the table is updated? The advantages would be that we would have all shaman information in one place and that each sighting would require only one edit. It'd be tricker to update, but not terribly difficult. A few comment tags in the code and an explanation in the article should be enough for most users to understand the process. — Elembis 04:54, 23 May 2006 (BST)

I'm not sure if the current table layout would work because it would become increasingly difficult to dig through the growing commented code to record new data. Will the data be stored under headings for each shaman to allow for quick section edits? --Lint 05:12, 23 May 2006 (BST)

Yes, code clutter could be a problem. I think the best way to limit it would be to leave the current table alone and put a big comment tag under it. It would look something like this (feel free to edit this yourself):

...
|-
|valign="top"| Zakano || {{GPS|70|446|26|453}}<br />00:52, 22 May 2006 (BST)
|}
<!--

PREVIOUS SIGHTINGS (Move replaced GPS/time information to its own line at the TOP of the appropriate list here)

Atok:

Movak:

Pabkim:

Zakano:
{{GPS|70|436|26|492}}<br/>00:44, 19 May 2006 (BST)

-->
</div>
...

This would be accompanied by a note on the article: "When you see one of these [wandering] shamans, please edit this article and move the old GPS and time to the 'Previous Sightings' comment tag that you will see." Even if we don't do this, wandering shamans should get their own section in order to make updates easier to make and also easier to summarize (since edit summaries for section edits automatically start with the section's name).

BTW, I previously changed "coordinates of spring" to "coordinates" because springs are invisible and inseparable from their respective village shamans. Traders, on the other hand, can apparently leave their huts, which is why the related column header on Trader reads "coordinates of hut". — Elembis 05:38, 23 May 2006 (BST)

I was just thinking... We could tear down the existing shaman pages to list only the most recent coordinate and timestamp. Then we hide the past positions wrapped in a <noinclude> tag. We then reference the individual pages using the composite page mechanics on the Shaman page. --Lint 06:02, 23 May 2006 (BST)