Difference between revisions of "Talk:Main Page"

From MK8
Jump to navigation Jump to search
 
(5 intermediate revisions by 2 users not shown)
Line 56: Line 56:
 
:: Yeah, that's the edit I meant.
 
:: Yeah, that's the edit I meant.
 
::* It's true that BIN is a rather generic file extension, though the MK8 *.BIN files use a common format at least on the top level, organizing data in sections and then groups.
 
::* It's true that BIN is a rather generic file extension, though the MK8 *.BIN files use a common format at least on the top level, organizing data in sections and then groups.
::* I agree that too many formats were on the main page, but not because of the count, but because of the wiki introduction, which states it contains information 'dedicated to Custom Tracks, Texture Hacks and Custom Characters', so those formats not matching that content should probably not be visible on the main page. However, it would be cool to jump to [[Category:File_Format]] when clicking the title of the blue File Format box, do you think that's possible? Otherwise I check on that if you like the idea.
+
::* I agree that too many formats were on the main page, but not because of the count, but because of the wiki introduction, which states it contains information 'dedicated to Custom Tracks, Texture Hacks and Custom Characters', so those formats not matching that content should probably not be visible on the main page. However, it would be cool to jump to Category:File_Format when clicking the title of the blue File Format box, do you think that's possible? Otherwise I check on that if you like the idea.
 
:: [[User:Ray Koopa|Ray Koopa]] ([[User talk:Ray Koopa|talk]]) 20:13, 6 May 2017 (UTC)
 
:: [[User:Ray Koopa|Ray Koopa]] ([[User talk:Ray Koopa|talk]]) 20:13, 6 May 2017 (UTC)
 +
 +
::: I have discussed this with Atlas. We'll keep the file format links for now, but when the first custom track has been released, then we'll add lists of all different types of custom tracks and then they will be removed. I also added a link to the category on the headline "File Formats".<br>--[[User:Wexos|Wexos]] ([[User Talk:Wexos|Talk]] | [[Special:Contributions/Wexos|Contribs]]) 21:36, 6 May 2017 (UTC)
 +
 +
:::: Just saw it, looks fine!
 +
:::: [[User:Ray Koopa|Ray Koopa]] ([[User talk:Ray Koopa|talk]]) 21:37, 6 May 2017 (UTC)
 +
 +
== Need formatting guidelines on File Format pages ==
 +
 +
I'm looking over the BFRES related pages to bring them up to date and add the missing subfile formats, but I'm never sure how to format field names, beyond some other stuff.
 +
* Should I Title Case them or rather Camel case them?
 +
* Should I include offset in the '''bolded variable name''' or not?
 +
* Should I write down when an offset is optional? In the end, theoretically every offset is optional, which can be seen in other games BFRES models; and I'm not really able to check every single MK8 model to make sure it's absolutely _never_ used or _always_ used in _MK8_. The general format basically results in "every offset can be 0 and then data isn't there". Sometimes offsets are valid but the corresponding array count is 0 (the offset points between other structures with no actual data then).
 +
* I now wrote the "End of BFRES String Table" offset is a File path name offset, as it was not actually the end of the string table. It pointed to an empty string which indeed always is the very last string in a table (possibly due to how it was sorted), but the string table ends later. - [[User:Ray Koopa|Ray Koopa]] ([[User talk:Ray Koopa|talk]]) 16:38, 29 May 2017 (UTC)
 +
 +
:: This is how I would prefer it:<br>The names of sections should be written as example "User data", not "User Data".<br>Bold text should be used where there is a lot of information, to identify the most important information. "'''User data''' offset" should be like that.<br>Like you said, all offsets are optional so it's not needed to have that information for every offset.<br>I don't know about the end of string offsets. An empty string will be the first string in the whole table, so then it shouldn't point to the start of the string table. I think this is just a special case.<br>--[[User:Wexos|Wexos]] ([[User Talk:Wexos|Talk]] | [[Special:Contributions/Wexos|Contribs]]) 20:12, 29 May 2017 (UTC)

Latest revision as of 20:12, 29 May 2017

Sharing data

At the moment, both Wikis share the users and the session cookies. What's about sharing the user pages (all pages prefixed by "USER:"). I'm not sure, if it is directly possible, but a frequently database copy is possible.

Wiimm (talk) 18:11, 5 August 2014 (UTC)

I think it is a better idea to let users choose for themselves, most userpages are designed especially for MKW CTs, if they want another userpage here they can get it. But for now a default template holding the link to the userpage of the normal wiki is the best solution in my opinion.
kHacker35000vr (talk) 21:37, 5 August 2014 (UTC)
I ran into a similar problem awhile back with profiles. The workaround was to 'hijack' the 'User:' namespace and set it and it's content to it's own database table (Which can be shared). The only issued lied within links - For instance, the link to GP Mario Beach on my profile at the Custom Mario Kart wiki doesn't link to the same place here. To work around this, I run a string-replace function based on the current URL (So if the user adds a link to their profile from Wiki1, the prefix for Wiki1 is added: [[Link]] becomes [[wiki1:Link]]). This profile system is heavily integrated with a toolset I've created (Including Blog and forum software, moderation system), I'd be happy to share it once it's complete. --SuperMario64DS (talk) 06:39, 17 August 2014 (UTC)
...Though alternatively, you could host a 'central' wiki (A 'Meta' wiki, if you will) that's neither this 'MK8 Wiki' or 'Custom Mario Kart'. You could then 'hijack' the namespace like before and set it to redirect to the equivalent userpage on the 'meta' wiki. If Custom Mario Kart plans to further branch with future games, then such a system may be more prominent. --SuperMario64DS (talk) 06:51, 17 August 2014 (UTC)

Interwiki 'language' links

I have added Interwiki links like the Wikipedia language links. This will change the semantics of the Interwiki links a little bit (see Sandbox).

The idea: similar articles in the other wiki are linked in the left column below the 'tools box'. If we want this, I try to replace the 'in other languages' text into 'in other Wikis'.

What do you think?

Wiimm (talk) 20:38, 11 August 2014 (UTC)

decided -- Wiimm (talk) 21:36, 17 August 2014 (UTC)

More cups dlc rumor?

It has been rumored someone hackers looked in the code and found

“ym_CupIconDLC_00_130x130^h.bflim”.

and some images of it. Could someone verify that, now that we have access to the filesystem? --Unsigned comment by Yoshinator (talk).

Starting Time

Actually I think it is too early for this wiki to be setup. I probably think it is appropriate to set it up when at least 2 CTs are out.--CustomArio (talk) 14:04, 3 September 2014 (UTC)

There is already one Texture Hack and one CT is announced. This wiki is also used for technical information about the game files. -- Leseratte (talk) 14:36, 5 September 2014 (UTC)
I thinks that good idea but could make section like "Preview" or "Work in progress" tracks?
It will give better idea who will make what, for example I have a track with large 3D model work and I would show it before it is possible to make it alive.
Simply to give an idea to Chadderz/Bean that they didn't do that for nothing and probably motive them but also to let others help first CTs to be good with ideas etc.
Thank you and if you need more details ;)
-- Baoulettes (talk) 01:57, 7 February 2015 (UTC)

Reason for removing several file formats?

What was the exact reason for removing several file formats? No editing summary was given. - Ray Koopa (talk) 16:57, 6 May 2017 (UTC)

I guess you mean this.
  • .bin is a general file extension since it stands for binary. It's like .dat, it's not a specific file format. It can contain any data.
  • I removed GTX because it's not as common as other formats, like BFRES and BFSTM. I'm not even sure if the file formats should be on the main page, but if it should it should only be some formats. I think there were too many.
--Wexos (Talk | Contribs) 19:49, 6 May 2017 (UTC)
Yeah, that's the edit I meant.
  • It's true that BIN is a rather generic file extension, though the MK8 *.BIN files use a common format at least on the top level, organizing data in sections and then groups.
  • I agree that too many formats were on the main page, but not because of the count, but because of the wiki introduction, which states it contains information 'dedicated to Custom Tracks, Texture Hacks and Custom Characters', so those formats not matching that content should probably not be visible on the main page. However, it would be cool to jump to Category:File_Format when clicking the title of the blue File Format box, do you think that's possible? Otherwise I check on that if you like the idea.
Ray Koopa (talk) 20:13, 6 May 2017 (UTC)
I have discussed this with Atlas. We'll keep the file format links for now, but when the first custom track has been released, then we'll add lists of all different types of custom tracks and then they will be removed. I also added a link to the category on the headline "File Formats".
--Wexos (Talk | Contribs) 21:36, 6 May 2017 (UTC)
Just saw it, looks fine!
Ray Koopa (talk) 21:37, 6 May 2017 (UTC)

Need formatting guidelines on File Format pages

I'm looking over the BFRES related pages to bring them up to date and add the missing subfile formats, but I'm never sure how to format field names, beyond some other stuff.

  • Should I Title Case them or rather Camel case them?
  • Should I include offset in the bolded variable name or not?
  • Should I write down when an offset is optional? In the end, theoretically every offset is optional, which can be seen in other games BFRES models; and I'm not really able to check every single MK8 model to make sure it's absolutely _never_ used or _always_ used in _MK8_. The general format basically results in "every offset can be 0 and then data isn't there". Sometimes offsets are valid but the corresponding array count is 0 (the offset points between other structures with no actual data then).
  • I now wrote the "End of BFRES String Table" offset is a File path name offset, as it was not actually the end of the string table. It pointed to an empty string which indeed always is the very last string in a table (possibly due to how it was sorted), but the string table ends later. - Ray Koopa (talk) 16:38, 29 May 2017 (UTC)
This is how I would prefer it:
The names of sections should be written as example "User data", not "User Data".
Bold text should be used where there is a lot of information, to identify the most important information. "User data offset" should be like that.
Like you said, all offsets are optional so it's not needed to have that information for every offset.
I don't know about the end of string offsets. An empty string will be the first string in the whole table, so then it shouldn't point to the start of the string table. I think this is just a special case.
--Wexos (Talk | Contribs) 20:12, 29 May 2017 (UTC)