@@ -78,49 +78,10 @@ Common problems with setup:
7878/csimgen (deprecated) - simulated the generation of a world generator.
7979/ctemprule - get and set variables which affect the workings of clientcommands. TempRules reset
8080 when you log out of a world.
81- /cenchant - manipulate the XP seed so that you can get the specified enchantments in an
82- enchantment table. This only works if the enchantment seed is cracked (see below).
83- First you specify the type of item you want to enchant, and then zero or more
84- enchantment specifications. There are two types of enchantment specifications:
85- `with` - This enchantment should be included in the enchantments on the item.
86- `without` - This enchantment should not be included in the enchantments on
87- the item.
88- In addition to the enchantment, you also specify the level of the enchantment
89- you would like. This level can either be an exact number, or a range in the
90- format min..max (e.g. `1..5`).
91- Once you run the command, the enchantment cracker may automatically throw items
92- onto the ground beneath you. Do not look anywhere else while this is happening,
93- as you may not be able to pick the items back up again. Once this is done,
94- follow the instructions the command gives you.
95- Examples:
96- `/cenchant diamond_sword with looting 3 without smite 1..5 without bane_of_arthropods 1..5`
97- `/cenchant fishing_rod with lure 3 with luck_of_the_sea 3`
9881/ctime - queries or changes the time client-side. All subcommands except `mock` and `unmock`
9982 only query the time. Using `/ctime mock <daytime> [doDaylightCycle]` starts mocking
10083 the time, and `/ctime unmock` stops mocking the time. Mocking the time means
10184 making it appear to be a certain time on the client-side only, while the server-
10285 side time (which is the time that matters for mob spawning etc.) is unaffected.
10386 `/ctime mock` is intended for builders to inspect their builds at different times of
10487 day.
105-
106- ===== ENCHANTING PREDICTION =====
107- WARNING: enchanting prediction is very cheaty and could get you banned from a server if an
108- operator finds out. However, given its client-side-only nature it's very difficult
109- to detect. There is also a chance it may be patched.
110-
111- Enchanting prediction can be used to see all items you would get on an enchantment in an
112- enchantment table before you actually enchant the item. To use enchanting prediction,
113- you must follow the following steps at the start of every enchanting session:
114- 1) run `/ctemprule set enchantingPrediction true`
115- 2) waste your first enchantment (enchant a cheap item)
116- 3) place another cheap item into the enchantment table (don't enchant it)
117- 4) block some more bookshelves with a torch
118- 5) repeat steps 3 and 4 until you're in state CRACKED_ENCH_SEED
119- 6) enchant the item (you can remove the torches now)
120- 7) repeat steps 3-6 once or twice more, until you're in state CRACKED
121- 8) there are certain common actions which will reset the process; clientcommands will
122- notify you when this happens. You just have to avoid doing these actions.
123-
124- Once you are in state CRACKED, you will be able to see all enchantments before you enchant
125- the item. You will stay in state CRACKED for the duration of the enchantment session unless
126- you do one of the actions from step 8. If this happens, you have to start from step 2 again.
0 commit comments