5/12/2023 0 Comments Brl cad commandssili Adds currently held item icon to sign or frame. Specifying the raw argument allows you to ignore jpeg enforcement if that is enabled in the configuration file. Specifying the all argument will restore all signs on the server. silrestore Restores an image on the sign that was broken during the last Rust update. silt Downloads a generated image with the given text and optional fontsize, color, bgcolor to be displayed on the sign you are currently looking at. Specifying the raw argument allows you to ignore jpeg enforcement if that is enabled in the config file. By the way.Chat Commands: /Config -Change What Elements You See On ScreenĬhat Commands: /Info - Shows All Our Info In GameĬhat Commands: /skin - opens the box, place the item to be skinned into the box and wait for skins to load Get VIP Only Skins By Getting A Package At Ĭhat Commands: /kit - see the full list of available kits for you /kit - choose a kitĬhat Commands: /backpack - open your own backpack /backpackgui - toggle whether you can see the backpack GUI buttonĬhat Commands: /mymini - Spawn a minicopter /nomini - Despawn your minicopter /fmini - Fetch your minicopterĬhat Commands: /bgrade 0 - Disable BGrade /bgrade 1 - Enable automatic Wood upgrades /bgrade 2 - Enable automatic Stone upgrades /bgrade 3 - Enable automatic Metal upgrades /bgrade 4 - Enable automatic Armoured upgradesĬhat Commands: /sil Download the image from the url to the server and display it on the sign you are currently looking at. I suppose I should automate the categorization I'm doing now (have you looked? does it look ok?), but I'm reading the pages as I go, and finding a few typos and things on the way too. When I'm done with MGED commands, I'll look for the docs you linked above and perhaps automate importing them. I'd use the categorization as a vechicle to drive the manual labor of getting the information in. Sean 02:43, 19 November 2009 (EST) Guess I misunderstood the question. At least, that's the case for the ones not already imported. The availability of docs depends on the command type, but most are either in manpage format (throughout the source tree, example here, or in docbook format here. How they are indexed and categorized isn't nearly as time-consuming as creating a page per command, though both tasks are exceptionally valuable (and tedious). Where is the documentation for these things anyway? - Ssd 08:27, 18 November 2009 (EST) I think we'd want to first at least have complete documentation for all commands. If you want a list sorted by function, just gotta plug at it one by one.like putting all the image conversion functions in at once or something. If you just want an alphabetized list, your best bet is to use the category system to do the heavy lifting and forget marking by purpose (or categorizing different purposes in different categories). Ideas on ways to streamline the process? - Sean 14:11, 15 November 2009 (EST) Though with over 400 commands, the task really begs for automation and scripting or a plugin. This page would be much better if it was formatted similar to MGED Commands, marking commands to their purpose or categorizing them or something.
0 Comments
Leave a Reply. |