|
|
|
|
|
Bem-vindo aos nossos novos jogadores brasileiros. Por favor leia
Difference between revisions of "Resources (RPCSS)"
From Sanctuary Shard
MamaWillow (talk | contribs) (Created page with "''It is our intention to implement in-game resource nodes which may be controlled via RPCSS. The kingdom pages provide some general fictional ideas as to what types of import...") |
MamaWillow (talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | ''It is our intention to implement in-game resource nodes which may be controlled via RPCSS. The kingdom pages provide some general fictional ideas as to what types of imports and exports are traditional for each of the kingdoms. Advanced in-game resources, such as magical ores, may eventually be claimed by different RPCSS player teams, thereby restricting player access to these resources. | + | ''It is our intention to implement in-game resource nodes which may be controlled via RPCSS. The kingdom pages provide some general fictional ideas as to what types of imports and exports are traditional for each of the kingdoms. Advanced in-game resources, such as magical ores, may eventually be claimed by different RPCSS player teams, thereby restricting player access to these resources. <includeonly>[[Resources (RPCSS)|Read More ...]]</includeonly><noinclude>[[category:RPCSS]] |
| + | |||
| + | This information is provide to players as a warning of intended functionality so that they may base their role-play around this eventual implementation. | ||
Latest revision as of 16:47, 18 June 2019
It is our intention to implement in-game resource nodes which may be controlled via RPCSS. The kingdom pages provide some general fictional ideas as to what types of imports and exports are traditional for each of the kingdoms. Advanced in-game resources, such as magical ores, may eventually be claimed by different RPCSS player teams, thereby restricting player access to these resources.
This information is provide to players as a warning of intended functionality so that they may base their role-play around this eventual implementation.
