8000 Fix typos in tutorials · uramer/CoreScripts@8f739f3 · GitHub
[go: up one dir, main page]
Skip to content

Commit 8f739f3

Browse files
urameruramer
committed
Fix typos in tutorials
1 parent 1ff394c commit 8f739f3

File tree

5 files changed

+8
-8
lines changed

5 files changed

+8
-8
lines changed

‎tutorials/CustomRecords.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ These are the main features differentiating generated records from permanent one
5252
If a generated record is not linked to anything, it is removed.
5353
* Generated records are only sent to players when necessary (inside a linked cell, a linked player is in the same cell, ...)
5454
* Generated records `refId` must follow a specific pattern `$custom_<storeType>_<number>`, e.g. `$custom_potion_2`.
55-
This allows other parts of CoreScripts to easily recognize that a particlar object is a generated record, and of what type it is.
55+
This allows other parts of CoreScripts to easily recognize that a particular object is a generated record, and of what type it is.
5656

5757
Give every player a note with their name in it:
5858
```Lua

‎tutorials/Introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,6 @@ It is generally a good practice to form each of your scripts as a single table,
2828

2929
As a quick introduction, [take a look at examples](Examples.md).
3030

31-
Consider joning the [TES3MP Discord server](https://discord.gg/ECJk293). There you will find:
31+
Consider joining the [TES3MP Discord server](https://discord.gg/ECJk293). There you will find:
3232
* `#scripting_help` here you can ask questions about writing TES3MP server scripts
3333
* `#custom_scripts` a catalogue of existing scripts. Use them as advanced examples, or maybe add your own scripts to the list!

‎tutorials/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
2. [Events](EventHooks.md)
55
3. [Timers](Timers.md)
66
4. [Chat commands](ChatCommands.md)
7-
5. [Synchronizing data](SynchonizingData.md)
7+
5. [Synchronizing data](SynchronizingData.md)
88
6. [Configuration and storage](ConfigurationAndStorage.md)
99
7. [Custom records](CustomRecords.md)
1010
8. [GUI](GUI.md)

‎tutorials/SynchonizingData.md renamed to ‎tutorials/SynchronizingData.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
The data is stored on the server using instance of classes [Player](#players), [Cell](#cells) [WorldInstance](#world). Specifically, all of the long-term information which gets kept between server restarts is in the `data` field of each instance.
66

7-
However, simply changing the `data` table of an object will only only alter that information on the server. To distribute it to the players' clients, you need to call a relevant `Load` function. There are too many to give a compehensive list here, so I will provide a few examples and leave the reader to explore source code for the remaining options. [scripts/player/base.lua](../scripts/player/base.lua), [scripts/cell/base.lua](../scripts/cell/base.lua).
7+
However, simply changing the `data` table of an object will only only alter that information on the server. To distribute it to the players' clients, you need to call a relevant `Load` function. There are too many to give a comprehensive list here, so I will provide a few examples and leave the reader to explore source code for the remaining options. [scripts/player/base.lua](../scripts/player/base.lua), [scripts/cell/base.lua](../scripts/cell/base.lua).
88

99
Altering `data` tables doesn't directly change the values stored on disk either. For them to stay after server restart, you need to eventually call either `SaveToDrive` or `QuicksaveToDrive` function (if you are not sure which one to choose, use `QuicksaveToDrive`). Keep in mind that file operations are much slower than almost anything else you could do, so perform them as rarely as possible (e. g. to prevent data loss due to a crash, or when unloading data from memory).
1010

@@ -44,7 +44,7 @@ end)
4444
```
4545

4646
Some regularly updated data is not passed to Lua scripts each time it changes.
47-
You have to call `Players[pid]:SaveCell` for current cell and location, and `Players[pid]:SaveStatsDynamic`for curent and total health, magicka and stamina.
47+
You have to call `Players[pid]:SaveCell` for current cell and location, and `Players[pid]:SaveStatsDynamic`for current and total health, magicka and stamina.
4848
```Lua
4949
customEventHooks.registerHandler('OnCellLoad', function(eventStatus, pid)
5050
if eventStatus.validCustomHandlers then
@@ -57,7 +57,7 @@ end)
5757

5858
## Cells
5959

60-
Currently active cells are stored in the `LoadedCells` global table, with `cellDescription`s as keys. Unlike the players, they get unloaded from memory quite ofen - whenever there are no players in a cell.
60+
Currently active cells are stored in the `LoadedCells` global table, with `cellDescription`s as keys. Unlike the players, they get unloaded from memory quite often - whenever there are no players in a cell.
6161

6262
Remove all pillows from a cell, whenever it is loaded
6363
```Lua

‎tutorials/Timers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Timers
22

3-
Timer functions are provided as a global `timers` table. All of them accept delay in milliseconds, but you can use [`time` functions](#time-unit-conversions) to convert diffirent units.
3+
Timer functions are provided as a global `timers` table. All of them accept delay in milliseconds, but you can use [`time` functions](#time-unit-conversions) to convert different units.
44

55
## Timeout and Interval
66

@@ -88,7 +88,7 @@ customCommandHooks.registerCommand("exit", function(pid, delayMinutes)
8888
end
8989

9090
timers.WaitAsync(delay)
91-
printRemaingingDelay(0)
91+
printRemainingDelay(0)
9292
tes3mp.StopServer(0)
9393
end)
9494
end)

0 commit comments

Comments
 (0)
0