User talk:JulienDethurens

WARNING: Do not use the edit button at the top. To add a subject, use the + button at the top. To reply to a subject, use the corresponding button next to the subject's header. DO NOT USE THE EDIT BUTTON AT THE TOP!

You can find archived talk from this page here

Archive

• 29 April 2012

Deleting tutorials

Are you sure this is a good idea? While the tutorials are specific, having a set of specific tutorials helps get new scripters into the hang of finding a problem and solving. Without any "real" code, it's much harder to get started.

NXTBoy (talk • contribs)

07:11, 25 April 2012 (UTC)

We already have examples in our non-specific tutorials, so that's not a problem. I didn't nominate them all for deletion either, I only nominated those who were clearly too specific. --JulienDethurens 17:06, 25 April 2012 (EDT)

I say no. I think that unless you have fun, and learn from doing specific things, you won't learn at all. The minecraft wiki, and every other game wiki (or engine wiki) has specific tutorials to do specific things. That's what makes it interesting, and keeps people reading. No one wants to read about data structures for hours upon end. People want to learn about stuff like making a catapult, and then take the skills learned from that, and apply it to something new. - Quenty (talk • April 25)

• The policy is rather clear. We aren't doing tutorials on how to make specific items. We can do tutorials on more general things, and people can learn those general things, and the combined new knowledge can be used to make specific items. For example, How to make lava is an overly specific topic. That should/will be deleted. That page combines various general things that we can have/should have tutorials/pages on. For example:

• Adding objects to a place
• Using events, such as Touched (Event)
• Using the Game hierarchy

Hope that clears it up.--Gordonrox24 | ^Talk 18:39, 25 April 2012 (EDT)

Meh. Seems kind of boring. Oh well. Perhaps we should atleast explain when explaining those other concepts the general role they play when being used as such. Like a list of common things it is used for. That way, when players search 'Lava', they atleast get instructions, instead of thinking 'The wiki sucks'. - Quenty (talk • April 25)

I wouldn't have a problem with a section on some pages explaining the practicality of them.--Gordonrox24 | ^Talk 19:37, 25 April 2012 (EDT)

May I also suggest:

• Adding a lot more links (This is how I get pulled into Wikipedia marathons
• Adding an object list to the end of all object pages to encourage traversing, exploring, learning, and more views. It looks nice, and is a standard navigation method of Wikipedia.

Example:

Classes
Parts:	Part,  WedgePart,  CornerWedgePart,  TrussPart,  SpawnLocation,  Seat,  VehicleSeat,  SkateboardPlatform,  FlagStand
Part Equipment:	SpecialMesh,  BlockMesh,  CylinderMesh,  FileMesh,  Decal,  Texture,  Fire,  Smoke,  Sparkles,  ClickDetector,  CharacterMesh,  Hole,  MotorFeature
Bodies:	BodyAngularVelocity,  BodyForce,  BodyGyro,  BodyPosition,  BodyThrust,  BodyVelocity,  RocketPropulsion
Gameplay:	Player,  Team,  Humanoid,  Tool,  HopperBin,  Flag,  Backpack,  StarterPack,  StarterGear,  Accoutrement,  Hat,  Camera,  Explosion,  ForceField,  Message,  Hint,  Sound,  Dialog,  DialogChoice,  Sky
Scripts:	Script,  LocalScript,  CoreScript,  StarterScript
GUI:	ScreenGui,  Frame,  TextLabel,  TextButton,  TextBox,  ImageLabel,  ImageButton,  BillboardGui, File:StarterGui icon.png StarterGui, File:PlayerGui icon.png PlayerGui,  CoreGui
3D GUI:	Handles,  ArcHandles,  SurfaceSelection,  SelectionBox,  SelectionPartLasso,  SelectionPointLasso,  FloorWire
Joints:	Snap,  Glue,  Weld,  Rotate,  RotateP,  RotateV,  Motor,  Motor6D,  VelocityMotor,  ManualGlue,  ManualWeld
Values:	Configuration,  BoolValue,  BrickColorValue,  CFrameValue,  Color3Value,  DoubleConstrainedValue,  IntConstrainedValue,  IntValue,  NumberValue,  ObjectValue,  RayValue,  StringValue,  Vector3Value
Services:	DataModel,  Workspace,  Players,  Lighting,  Teams,  Debris,  SoundService,  InsertService,  BadgeService,  TeleportService,  TerrainService,  Chat,  JointsService,  ScriptContext,  RunService,  PhysicsService,  CollectionService,  ControllerService,  GuiService,  ContentProvider,  Selection
Settings:	GlobalSettings,  Authoring,  DebugSettings,  FastLogSettings,  GameSettings,  LuaSettings,  NetworkSettings,  PhysicsSettings,  RenderSettings,  TaskScheduler,  UserSettings,  UserGameSettings

• Adding interesting ROBLOX history and information that generally talks about ROBLOX, such as what 'Noob' means, etc, since it's used basically everywhere on ROBLOX
• Standardize a navigation method per subjects.

I would be happy to help with all of theses. - Quenty (talk • April 25)

I nearly crashed the wiki when I tried to add that navbox to object pages. Before making any major changes, I'd like to come up with a less template-intensive solution for API documentation. --Anaminus 20:04, 25 April 2012 (EDT)

Quenty, the wiki shouldn't really be used to document ROBLOX itself, only building and scripting. Builderman's help pages should document ROBLOX, we should document building and scripting and the blog should document news and be used for history. We could basically say these three sources of information work together. You can probably notice easily how the wiki, the blog and builderman's help pages are filled with links to each others (blog posts often have links to the wiki and the wiki give links to many blog posts, same with builderman's help pages). There isn't really anything wrong with the current ROBLOX pages, but it'd be better to not make too much of these, because they're not really supposed to be on the wiki. --JulienDethurens 20:10, 25 April 2012 (EDT)

Also, just because we shouldn't have instruction pages on specific subjects doesn't mean we can't give pratical uses of what we teach. We can make instruction tutorials on non-specific things (like on how to use plugins, terrain, GUIs or any other ROBLOX feature) and give examples in our tutorials. I also think it would be a good idea to give some links to the Cookbook and to add more things to it. After all, Camoy's cookbook contains lots of useful examples that are well described. They are a little specific, but it is precisely an instruction book. It doesn't put them all in different pages, but instead groups them, so it's fine, especially since they are well explained. Perhaps we could give links to it for examples that relate to things we're explaining in tutorials. --JulienDethurens 20:13, 25 April 2012 (EDT)

I think it's really a discussion between what the wiki is. Is it an instruction booklet, or a wiki? If it's an instruction booklet, or a help booklet, we should stop calling it a wiki. If it's a wiki, then it's about ROBLOX in general, i.e. The ROBLOX wiki. I think that the ROBLOX wiki should be a wiki, i.e. we document ROBLOX (In general), and teach not only about ROBLOX's API and building (Although, really, it's just the API right now), but also about how to gain money, status, and what/how to do small certain things. When explaining stuff, like how to make a plane, you just say 'How' to do it, and point them out to the right API. I think we shouldn't talk about specific players, but talk about general creations in time spawns, like 'VIP shirts' or 'WTRB' or 'Camera Manipulation' or 'Group Projects', and how to use, and apply them. We should INSTRUCT on how to do stuff players SEE on Roblox. Like, how to build up a big group, and standard strategies employed. This shoudn't make the wiki more cluttered, or harder to learn from, but it should make it more interesting. For now, players are in the dark, wondering, WTH do I do?, or 'What's a group'? We need to create a documentation of every feature that ROBLOX offers, and the best way to gain for use that feature, and make it MORE THEN AN API BOOKLET! (Which is boring). I'm now done rambling. - Quenty (talk • April 30)

- Quenty (talk • April 30)

Your Guide

I would suggest, instead of saying 'I'll talk about this later' in your guide, say ' For more information about local variables, see here '. This will help players to stop being confused. The problem might be, them getting off topic, and stuff. Also, I would suggest including a short challenge after each section, so they know they can do it, and so they actually try a demo. Otherwise, they just say they don't get it. If you don't actually type stuff out, then you usually won't get it. :D - Quenty (talk • April 30)

Yeah, I keep saying that I'll explain stuff later. The problem is that every Lua feature relies on other feature, so I need to explain a part of a feature, then another part, then another part, etc... --JulienDethurens 23:55, 29 April 2012 (EDT)

Archive your talk

Page load time is a bit slow. Just an idea. :D - Quenty (talk • April 30)

Archived. :) And I've changed to a new archiving system too. Moving it all on another page (or even on many subpages) makes it become a mess after some time, so, from now on, I'll just use the history. I wish the devs would just install the LiquidThreads extension or something like that, though. --JulienDethurens 23:54, 29 April 2012 (EDT)

This isn't a forum. Might be kind of cool though. - Quenty (talk • April 30)

I know. However, it has been pointed out many times that MediaWiki wasn't really created for discussion. I've heard they've thought up something for a future release about that, but I didn't bookmark the page. I'll try to find it back through Google. --JulienDethurens 00:56, 30 April 2012 (EDT)

Yeah.... Hmmmmm.... - Quenty (talk • April 30)

New 'Continue' button for your cookbook

I designed a new 'Continue' button to go forward or backward in a cookbook, which just seems more intuitive and nice. Except for the auto-coloring of the links.

What do you think? - Quenty (talk • April 30)

It's not a cookbook, are you crazy? It's a scripting guide! Not a cookbook! Huh, anyway, I'm going to edit the CSS a little.. --JulienDethurens 01:03, 30 April 2012 (EDT)

My CSS just got totally changed, and removed, and stuff by Anaminus. - Quenty (talk • April 30)

Hey, we got new extensions!

Including a few very much wanted ones. YAY! - Quenty (talk • April 30)

Erm, did we? Doesn't look like it.

NXTBoy (talk • contribs)

17:12, 1 May 2012 (UTC)

We did get new extensions: Asirra, ConfirmEdit and Google Analytics Integration. But I don't think we can consider these three extensions as "a few very much wanted ones"... --JulienDethurens 16:51, 1 May 2012 (EDT)

Yeah, also, the ToS now slides. :D I wish I could have access to the server of this wiki... :D - Quenty (talk • May 1)

Stop.

Please stop nominating user pages for deletion. They aren't a priority, and really don't need to be deleted. Furthermore, I think your recent edit to the delete template has stopped the pages from being added to the pending removal category. All this is doing is creating more work for us, that really isn't necessary. Thanks.--Gordonrox24 | ^Talk 21:02, 5 May 2012 (EDT)

These pages are causing a problem for the wiki. No, really, they are. Not long ago, I set up a goal for myself: cleaning up all the maintenance reports in the special pages as much as possible. The problem with this is that many of them are spammed with links coming from user pages and the like. So I decided to clean all the user pages, so we can actually get useful maintenance reports instead of them being spammed. --JulienDethurens 21:05, 5 May 2012 (EDT)

I was almost done nominating them all for deletion... can I finish it? :( --JulienDethurens 21:11, 5 May 2012 (EDT)

Meh. Didn't see this till now. I'll stop too. - Quenty (talk • May 6)

I'm sad because I had to stop while I was almost done... I think there were only 50 pages left or so... Wish I only had noticed the "You have new messages" banner after deleting some more pages... :( --JulienDethurens 21:16, 5 May 2012 (EDT)

Hmm... Can I nominate 5000 files for deletion? I mean, deleting the files is more important than deleting the user pages, right? :) --JulienDethurens 21:19, 5 May 2012 (EDT)

No. Do not nominate 500 pages of anything for deletion at once. I seriously need you to tone it down. I understand the maintenance issue, however, as I said, that is not a priority and is just creating massive amounts of work at the moment. --Gordonrox24 | ^Talk 21:29, 5 May 2012 (EDT)

I wish I could delete them myself. :( Ok, I'll only delete those who directly cause a problem for maintenance, and I'll remove red links in pages... D: --JulienDethurens 21:32, 5 May 2012 (EDT)

I or Julien would be happy to do it, but I know your trust probably won't necessarily be extended that far. - Quenty (talk • May 6)

Place

Since my place got hacked, should I just open source it? Or would that make it look like I did hack it? Because that guy is making it look like I hack his place. I'm annoyed that he stole my images and buildings.... - Quenty (talk • May 6)