TibiaWiki
Tag: sourceedit
Tag: sourceedit
Line 241: Line 241:
 
[[User:Cauli92|Cauli92]] ([[User talk:Cauli92|talk]]) 09:39, May 26, 2017 (UTC)
 
[[User:Cauli92|Cauli92]] ([[User talk:Cauli92|talk]]) 09:39, May 26, 2017 (UTC)
 
----
 
----
  +
I had the same idea some days ago when I was editing a few game world pages. Go ahead, Six! :)
  +
  +
[[User:Hunter of Dragoes|<font color="Blue">Hunter of Dragoes</font>]] <small>([[User talk:Hunter of Dragoes|<font color="Blue">Talk</font>]] · [[Special:Editcount/Hunter of Dragoes|<font color="Blue">Contribs</font>]] · [[TibiaWiki:Administrators|<font color="Blue">Admins</font>]])</small> - 12:53, May 26, 2017 (UTC)

Revision as of 12:53, 26 May 2017


Welcome

Feel free to discuss things among admins. Ask things to admins, propose new ideas etc. Reporting a vandal can also be perfectly done here, but is not really the intention of this page. Also note that this page doesn't have the same function as TibiaWiki talk:Community Portal.


History section on content pages

Hey guys. I'd like your opinion on adding a history section to pages. Currently we link to history subpages. Under the new system the subpages would stay for ease of editing but they would be included on the pages. The format of these history pages would be very different. We would need a standard for formatting them.

I have a working example of what I'd like to see: A Sweaty Cyclops. Notable changes:

  • History template gone.
  • Formatting: bullet points for core changes and indenting for elaboration.
  • Headings: no more "Origin", "Ice protection" etc. headings; the headings currently describe the changes (what), but they should describe the version (when). If Pair of Earmuffs receives another ice protection adjustment where would that go? Versions that introduce changes to an item should have a unique header.

Of course this would be a long-term change. All history pages would need to be adjusted. The sooner we agree on a format the sooner we can get it done. -- Sixorish (talk) 13:49, May 27, 2015 (UTC)


I think we can all agree the history pages didn't work out what was intended when the format was created in the first page. The idea to have an origin for every history page wasn't really usable, either "introduced in update xx" (but we have implemented for this). Only a few pages have interesting origin stories.

So I agree a change is needed. Moving the content to the main articles seems reasonable, given that most history pages are very short right now, it saves a click if you don't have to navigate to them. I would suggest just completely moving their content instead of including (this would increase speed? or it doesn't matter after it's cached?).

It's a big project indeed, if every edit would be needed to be done manually. But I agree it's needed. I agree with your format, although I can imagine the bullet point list looks a little technical to most people. -- Bennie (talk ~ fellows) 14:00, May 27, 2015 (UTC)


We should always think on what is the best for our visitors to read and to edit. Thus, moving the history to the content page seems the best option.
Thanks Six for putting time and energy on this!

Hunter of Dragoes (Talk · Contribs · Admins) - 02:22, May 28, 2015 (UTC)


Just to follow up on this old discussion, currently I'm working on history pages. What would you think is better:

  1. History section is always shown, if no history is available this is displayed in italic text;
  2. History section is hidden by default, but is displayed if parameter exists.

The advantage of the first option is editors know they can add history on pages which don't have it, but visitors might be annoyed by the message there is no history on 90% of our pages. -- Bennie (talk ~ fellows) 11:13, August 24, 2016 (UTC)


I'd go for the second option because of exactly what you said.

Hunter of Dragoes (Talk · Contribs · Admins) - 22:15, September 12, 2016 (UTC)


Ok, this has been implemented in all relevant infobox templates. Only some item history subpages need to be merged with their main item page. -- Bennie (talk ~ fellows) 08:00, September 27, 2016 (UTC)


All remaining pages using Template:History have been merged. -- Bennie (talk ~ fellows) 15:08, October 14, 2016 (UTC)


New item parameters

Hey guys,

I am working on the Updates/10.94 weapons. This is a huge project, there are 120 wiki pages needed, from which only one third are created up till now. There is something else as well, I wanted to add six new parameters to Template:Infobox Item:

  • crithit_ch
  • critextra_dmg
  • manaleech_ch
  • manaleech_am
  • hpleech_ch
  • hpleech_am

This will have the advantage to query for these properties with DPL, to have them in separate table columns and not everything grouped in the attributes column. Like previously discussed, this should also be done with all the damage modifies like "axe fighting + 1". Any objections or thoughts? -- Bennie (talk ~ fellows) 09:19, August 24, 2016 (UTC)


Yes, go for it! As I stated last year, I believe skill and speed modifiers should also have their own individual parameters.
Let me know if there's anything I can do to help.

Hunter of Dragoes (Talk · Contribs · Admins) - 22:24, September 12, 2016 (UTC)


Ok, I implemented the six new parameters and made separate DPL templates to list them. I will start adding new parameters soon and include skill and speed modifiers as well. -- Bennie (talk ~ fellows) 08:01, September 27, 2016 (UTC)


Node-count limit

Does anyone know how to extend the node-count limit or how to circumvent it?

Affected pages:

Hunter of Dragoes (Talk · Contribs · Admins) - 22:47, September 12, 2016 (UTC)

It's called preprocessor node count. Kirkburn said this is not something we are likely to be able to raise (at least in the short term) and suggested us to look into ways to reduce the complexity of the page - perhaps by splitting it into more pages, or reducing the number of template calls it makes.
How can we reduce the number of template calls? Should we remove Loot and Dropped By columns from those pages (and all similar pages in order to keep the standards)?
Hunter of Dragoes (Talk · Contribs · Admins) - 16:01, September 17, 2016 (UTC)
Seems to work, tested on Physical Damage/Neutral. I don't know what columns are most important to keep.

-- Bennie (talk ~ fellows) 17:49, September 17, 2016 (UTC)


Two more pages added to the list. By the way, shouldn't there be a Loot namespace for such pages?

Hunter of Dragoes (Talk · Contribs · Admins) - 09:14, September 28, 2016 (UTC)


Re: namespace - No way. We're limited in the number of custom namespaces we can have (2 I think). Besides, these Loot pages are outdated and should probably be removed completely since they create huge maintenance jobs (if a creature's loot table is modified, all loot pages with that creature have to be updated) and they're seldom used (probably because they aren't up to date?). -- Sixorish (talk) 16:20, November 19, 2016 (UTC)


Just tuning in to say that I agree with Six regarding the pointlessness of those loot pages. -- Wouterboy (talk) 17:04, November 19, 2016 (UTC)

Renaming category for NPCs

Hey all, I plan to rename the category: Category:NPCs in Tibia to Category:NPCs, which is more logical. Are there any objections to abstain from doing so? -- Bennie (talk ~ fellows) 12:08, November 27, 2016 (UTC)


I believe Category:NPCs in Tibia is meant to be applied only to individual NPCs and Category:NPCs is meant to apply only to groups of them. However, the latter is barely used for its intended purpose, as you can see from the low amount of pages that are listed under it. The question you should ask yourself is whether this special group-sorting category is even necessary, especially given the fact that categories such as Category:NPC Locations and Category: NPC Occupations have taken over this role for a large part. Based on the outcome of those ponderings you can then decide either to carry out the move or to abandon it. -- Wouterboy (talk) 16:21, November 27, 2016 (UTC)


Ok, I think I made all necessary arrangements to do the change. Soon I will let my bot crawl over all wiki pages to do this search-and-replace. Hopefully this will catch them all and break nothing. -- Bennie (talk ~ fellows) 17:19, November 27, 2016 (UTC)


Template:Infobox Item and Imbuing

I'd like to propose the removal of the parameter imbuable from the item template. Items are bound by the functional dependency imbuement → imbuable; an item is imbuable if and only if imbuement > 0. This parameter is not declared on non-imbuable items. Thus, we're storing the same information (imbuable) twice. While at it, I would also like to propose the imbuement parameter be renamed to imbueslots (preferred) or imbuements (plural).

Any objections to this? (Bennie, if you have time, I could use the service of your bot for this)

-- Sixorish (talk) 15:27, December 16, 2016 (UTC)


I agree with the removal of the imbuable parameter and rename imbuent to imbueslots. I'll set up my bot to do this soon. On a sidenote, how did you obtain the imbuements information? I couldn't find a list on the test server forum, but they also changed the items a bit since then. -- Bennie (talk ~ fellows) 17:15, December 16, 2016 (UTC)


I had 94ish items and then I realized they added the number of slots to the market. -- Sixorish (talk) 03:35, December 17, 2016 (UTC)


The market is a good source of info, didn't realise that as well. My bot is currently editing the 200 pages. -- Bennie (talk ~ fellows) 10:17, December 17, 2016 (UTC)


Tibia's 20th Anniversary

There's not a word about Tibia's 20th Anniversary on the front page of the tibia wiki. Even the events section says "This month, January, there are 2 events: New Year Time and Bewitched." Surely, Tibia's 20th anniversary is worth at least mentioning as an event.

Pattre Kempe (talk) 07:19, January 11, 2017 (UTC)

CreatureDroppedBy Bot Proposal

Hey guys,

I wrote a bot proposal. My idea was to write this bot in Java, since I learned it recently and use it daily on my job now. Anyways, a lot of programming languagues already have API access libraries. Then I can just run the bot ~weekly and maybe more during updates. If you have any feedback on this idea I'd like to hear them. -- Bennie (talk ~ fellows) 09:50, February 18, 2017 (UTC)


i think this is a great idea, the only note i can think of right now is to eliminate certain special loot (silver raid tokens, party wall snake,party wall tinsel, party lampions - or during events like anniversary old rugs)

Vapaus (talk)


I think it would be good but there are two scenarios that this will cause issues:

There are of course workarounds to this:

  • Have all edits marked as pending review; post the list of changes to be made and allow editors to review these before they go live. They can edit the page to remove that item (hopefully making it impossible for your bot to find this issue next run).
  • Post all changes made to an article for review in post.

-- Sixorish (talk) 14:47, February 18, 2017 (UTC)


Thanks Vapaus, that's a good point. I think there is a list of filtered items in the loot parser which I can use and also add stuff like Gold Coin which we don't list a droppedby list of.

Sixorish, that's a good point but will only be an issue if I'd let the bot run without any double-checking. I'll have to look for false positives in the beginning and think of ways to filter them later.

I (almost) have a first working version. -- Bennie (talk ~ fellows) 13:32, February 19, 2017 (UTC)


I thought the plan was to run it as a weekly cron job, fully unmanned; if you're checking the changes yourself, that shouldn't be an issue. Are you looking for help on the coding side of things? -- Sixorish (talk) 14:21, February 22, 2017 (UTC)


Well, a fully unmanned situation would be ideal, but requires some extra measures to prevent situations to happen, like you described.

I marked you as a collaborator so you can help if you want. But first I'm going to make the code a little cleaner, up until now I was just trying to get something to work, but I can do better than this (I'm currently reading "Clean Code" by Robert Martin which has some really nice insights, I can recommend it). -- Bennie (talk ~ fellows) 19:12, February 22, 2017 (UTC)


Reachable / Unreachable - Debug Tiles?

With the recent updates to the tibia-maps project, a few reachable/unreachable tiles were uncovered by Svargrond arena. I am guessing these tiles are related by some functional purpose, but what is it? Can they be reached or were they just temporary teleportation tiles while the debugging process was active; and if they cannot be reached, do they still exist? (If so, why?)

If they are related for some reason and still exist today, then surely other related game functions (seems to be time-based events?) have their own as well.

Here are some other boss rooms that have candidate tiles (or maybe not):

-- Sixorish (talk) 12:14, May 23, 2017 (UTC)


I've noticed similar tiles on PvP and PvE arenas, like here, here, here, here and here.

The tiles you mentioned in Svargrond arena have always been there and Cip never tried to hide them on the maps published to promoted/supported fansites (check the early versions of File:Minimap Floor 7.png).

Here's a "screenshot" of Svargrond arena's secret tiles:
Svargrond arena secret tiles

I believe characters are either teleported there in order to trigger the arena/boss event (making monster spawn, starting timers) or when the time is over (before being teleported somewhere else).

Other places:

Hunter of Dragoes (Talk · Contribs · Admins) - 14:59, May 23, 2017 (UTC)


Yes, they are used to trigger the spawning of certain creatures or to effectuate changes to the environment. I remember a post on the forums some time ago by someone who had figured out that the separate stages of the orcish raid on Zzaion are triggered by rats spawning on top of such switchplates. -- Wouterboy (talk) 02:21, May 24, 2017 (UTC)

BattlEye integration

Should we change Template:Infobox World to add a boolean field to represent whether or not servers are protected by BattlEye? -- Sixorish (talk) 05:22, May 26, 2017 (UTC)


Well, it depends. Won't all worlds get BE protection in a few months? Your suggestion would only make sense if for an extended period of time only a part of the servers are BE protected. -- Bennie (talk ~ fellows) 08:34, May 26, 2017 (UTC)


Seeing how CIpsoft makes those changes, I think it's a good idea to have BattlEye column, if they keep activating it on few by few worlds, people will get lost eventualy, so even if it has to be reversed in near(half a year, year?) future, it could be pretty useful for now. Cauli92 (talk) 09:39, May 26, 2017 (UTC)


I had the same idea some days ago when I was editing a few game world pages. Go ahead, Six! :)

Hunter of Dragoes (Talk · Contribs · Admins) - 12:53, May 26, 2017 (UTC)