User talk:CloneTrooper1019


Hello. I would like to welcome you to the wiki and introduce you to the way it is organized. It is a bit difficult because of the limitations of the current documentation system to understand how to use it and document objects, so I will do what I can to refer you to useful resources to learn how to contribute to this wiki. I will assume that you are already comfortable with wikimarkup and MediaWiki; if this is not the case, please take a look at MediaWiki's help.

First, it would be good that you read the editing policy; more than being a policy, it includes some useful tips and indicates what style should be used on articles on the wiki. You should also look at the template information page, which, while a bit outdated, describes how to use the different templates on the wiki; without this page, it is impossible for someone with not much experience of the wiki to understand how to do non trivial things in tutorials. To figure out how to document parts of the API, you can look at the guide Anaminus created, but while you can document things right now if you want, it is not very useful because the current system will be replaced soon by a better system. You will also probably be interested in an essay I wrote about documenting things on the wiki.

If you are unsure what style you should use in articles and the pages mentioned do not help, you should look at Wikipedia's manual of style and follow the advice given there.

You can see what is happening on the wiki and what is being discussed on the general discussion page. ― Mark Otaris (talk) 23:59, 20 January 2014 (UTC)

Template: Clr

Hey Clonetrooper. Just writing on your talkpage to notify you I've marked your 'Clr' template for deletion, as there's already a template which exists to do what yours does, which is named clear floats. You should use that template instead. -- Quorum (Talk) 01:29, 22 January 2014 (UTC)

Position (Property)/Input

Hey, just writing to your discussion page to notify you that I've declined your edit to Position (Property)/Input in favour of your original submission. I've done this as I really do not see why it requires a link to itself, especially on its own page. The page is also already linked in the "See Also" section of Position (Property) making the link redundant in my opinion, with a detailed description making much more sense. -- Quorum (Talk) 05:58, 25 March 2014 (UTC)

API:Class/Player changes

Don't think I agree with this strategy - far too easy to omit a crucial property, such as you did there w'ith .Name. Why are we removing these members completely rather than just hiding them?
NXTBoy (talk • contribs)
18:25, 30 December 2015 (UTC)
Seems like a bad idea in general to do this. For example, Backpack only exists when the character exists, or around that time anyway. So I use FindFirstChild to check for its existence. Hiding them like that gives the impression the members don't exist at all. On some objects they really are useless to mention like KeyCode, but on Player and similar they are still important. Legend26 (talk | contribs) 20:32, 30 December 2015 (UTC)

You guys make good points; this was definitely an oversight on my end. I'll undo those changes. CloneTrooper 1019 (talk) 06:20, 31 December 2015 (UTC)

"We need to keep this hack in for certain class pages like RbxGui and Terrain."

Next time (and this time) you introduce code for a hack, can you add a comment linking to where the hack is needed, so that someone else can look into removing it later?
NXTBoy (talk • contribs)
20:36, 19 September 2016 (UTC)
Sure. Sorry for the inconvenience, not a lot of people have been messing with the wiki besides me for the past year (besides Memory Address).
CloneTrooper1019 (talk) 12:20, 20 September 2016 (UTC)