|
How
To Play / Known
Issues / Internal
Messages / External Messages
/ Adding Cells
How
To Play
I'll assume you've followed the instructions in the "First
Steps" section. Here's what you do know. Follow these steps to make
sure it's going to work.
NOTE: THIS HAS ONLY BEEN TESTED
FOR A CLEAN INSTALL OF OBLIVION. I HAVE NO IDEA HOW OTHER MODS WILL IMPACT
THIS ONE
ALSO: DON'T RESIZE THE CLIENT....I
FORGOT TO FIX THAT....*SIGH*....IT WILL BREAK IT!
SUPPORTED CELLS: IMPERIAL CITY,
ANVIL, CHORROL, TAMRIEL, BRUMA, BRAVIL, LEYAWIIN, CHEYDINHAL, SKINGRAD
| 1) |
Run the MultiTES4
client. Move it so it is positioned at the bottom right of your
screen. |
| 2) |
"Connect" to a server that is running.
Now click the "Synchronise" button (it will fail,
but that's fine as it will retry). |
| 3) |
Quickly run Oblivion before the next retry (you have
45 seconds), but make sure you do so in "Windowed"
mode! IMPORTANT! (Oblivion doesn't allow context switching).
This is found under "Options" in the Oblivion launcher. |
| 4) |
Once it has loaded, load up a save game (the special
one you saved before). |
| 5) |
After several seconds, you should see a message in the
top left of your screen, saying something along the lines of "Player
# Initialised". This is good as it means the scripts are
activating properly. |
| 6) |
Now that you're ingame, wait for the client to retry
synchronisation with Oblivion. |
| 7) |
If you get to the "Injecting/Extracting Data..."
stage without the "Adjusting Failed!" stage, things
are working well. |
| 8) |
When another player connected to the server makes his
first move after you have connected, you should see a "Added
New Player To Game" message appear in the client's external
log. |
| 9) |
In a couple more seconds (in-game), you should see a
another message at the top left of your screen saying "Player
# has joined the game." The MultiTES4 quest will activate
as well. It is recommended you make this you're active quest. |
| 10) |
Go find your friend (he will appear as a green marker
on your map and compass when you have the MultiTES4 quest active),
but remember it only works for exterior cells, such as Tamriel and
the main cities. You can technically add any cell you want (say you
want to explore alyied ruins with a friend), see the "Adding
Cells" section on this page. |
| 11) |
If everything appears to be working, then next time
you play, you can do so in "Full Screen" mode. Follow
the same steps as before. |
| 12) |
The server is flimsy at best. If you disconnect for
some reason, you will be able to connect again, but the game may be
broken. The server will be improved over time to handle disconnections.
The best result is when you only connect once. UPDATE: This has been
somewhat fixed, although I still wouldn't trust it ;-) |
| 13) |
WARNING: Do not save your game when
you are playing! If you save the game while MultiTES4 is playing,
you will not be able to use that save again for a multiplayer game.
Before you play, have a save game that you can load up if you die
(this is the one you made before you acrivated the mod). I intend
to fix this issue in a later release. You will know when a save game
is corrupt, as you will ALWAYS recieve the "Failed
To Find Injection Point!" message. |
| 14) |
Be patient, this mod will improve with time. |
Known
Issues
I know about the following problems, and I'll do what
I can to fix them as quickly as possible
|
Program Crashes When "Disconnect"
Clicked
|
HIGH
|
This has something to do with the external
thread not closing properly when it should be. I'll be looking into
this as soon as possible, as no-one likes a program that crashes ;-)
It shouldn't affect your computer at all, although you may want to
check that there isn't any instances of MultiTES4.exe running in the
background. Use your "Windows Task Manager" to check. |
|
All Bot Verifications Fail
|
MEDIUM
|
This happens when you have closed the client and re-opened
it (or synched then de-synched) without restarting the game. I'm actively
fixing this problem, and may not even be an issue in the first release. |
|
The Connection Seems Slow
|
FIXED
|
Things have only just starting working, so a lot of
optimisation has yet to take place. Be patient, as the mod is developed,
this will most certainly be fixed. My aim will be to have pings of
less than 100ms over a LAN at the very slowest. It's being looked
into. |
|
Interface Doesn't Relay Enough Info
|
LOW
|
The next version will fix some of the interface issues,
and will include a connection speed meter. |
Internal
Messages
Below you'll find an entire list of all the messages that
you may see in the 'Internal Log' when using the MultiTES4 client.
|
"Scanning For Oblivion..."
|
GOOD
|
The program is searching for an instance of Oblivion
currently running on your computer. |
|
"Oblivion Window Not Found!"
|
BAD
|
The scan attempt failed, you probably don't have Oblivion
running. |
|
"Failed To Synchronise!"
|
BAD
|
Because Oblivion wasn't found, the client couldn't synchronise
itself with it. |
|
"Retrying In 45 Seconds..."
|
GOOD
|
The client will try again in 45 seconds. It'll attempt
another scan for Oblivion. |
|
"Oblivion Found!"
|
GOOD
|
A window with the title "Oblivion" has been
found. This could be good or bad, as you'll see later on. |
|
"Oblivion ProcessID NOT Determined"
|
VERY BAD
|
Pray to your god that you don't get this message. If
you do, try a restart of your system and start again. |
|
"Oblivion Process Access Denied"
|
VERY BAD
|
I've never had this error before. If you do, it may
be because you don't have administrator access or something. From
my own experience that hasn't been a problem though. |
|
"Process Attach Successful!"
|
GOOD
|
Ok, the client has now attached itself to the Oblivion
window. Things are looking good. |
|
"Multiple Oblivion Windows"
|
BAD
|
The client has confused itself. You'll get this message
if you have any windows or applications open that have the same window
title as the Oblivion game itself. To fix this, simply close any programs
or folders that you have open titled "Oblivion", except
for the game executable itself. |
|
"Verifying Data..."
|
VERY GOOD
|
Good for you, the first part of the synchronisation
process has completed successfully, but don't open the bottle of champagne
yet ;-) |
|
"Shadow (some number) (some data) Corrupt!"
|
BAD
|
Ok, the program is trying to find the data injection
point for the other players. This message means that the memory value
isn't what it is supposed to be, but don't worry. The client will
try adjust itself to match the instance of your Oblivion. |
|
"Adjusting Failed!"
|
VERY BAD
|
The client couldn't make sense of the data from Oblivion.
This may happen because 1) You have de-synchronised the client and
then re-synchronised the client without restarted Oblivion. To fix
this, restart both Oblivion and the MultiTES4 client. 2) You have
been messing with the MultiTES4 mod file (*.esp). Re-download the
mod file, and try not to touch it with your grubby hands. Yes, I said
grubby. |
|
"Shadow (some number) Data Verified (Injection
Ready)"
|
VERY GOOD
|
The client now knows how to access the Oblivion data
to put a player into your game. The number corresponds to the player
number. Depending on the version, only one may by verified, but with
any luck all 8 (0-7) should be verified. The number that is verified
indicates the number of players that your client can support. |
|
"Failed To Find Injection Point!"
|
VERY BAD
|
A result from receiving the "Adjusting Failed!"
message. To fix this, follow the instructions for the "Adjusting
Failed!" error message. |
|
"Internal Thread Active"
|
GOOD
|
The thread that handles the injecting and extracting
of data has been created and is now running as required. |
|
"Failed To Create Thread!"
|
VERY BAD
|
You shouldn't get this message...ever... If you do,
then your system doesn't allow multithreading or something weird like
that. Perhaps you're just seeing things. |
|
"Injecting/Extracting Data..."
|
AWESOME
|
Everything is right with the world and as it should
be. The birds are singing and the sun has broken through the soft
fluffy clouds the litter the sky. The internals are up and running,
go grab that bottle of champagne. You kept it on ice, right? |
|
"Thread Closed Succesfully"
|
GOOD
|
When you click the "De-Synchronise" button,
if the internal thread is closed successfully, then this message will
be displayed in the internal log. |
External
Messages
Below you'll find an entire list of all the messages that
you may see in the 'External Log' when using the MultiTES4 client.
|
"Initialised Connection"
|
GOOD
|
The client has initialised a connection where it will
send the data as it is collected from Oblivion. This does not necessarily
mean that there is an active server at the address you have specified,
only that the connection on the client side is ready to be used. |
|
"External Thread Active"
|
GOOD
|
The thread that handles the sending and receiving of
packets has been created and is now running as required. |
|
"Attempting To Send/Recieve Data..."
|
GOOD
|
As the message suggests, the client is now actively
sending and expecting packets from the address you specified in the
edit field. |
|
"Failed To Create Thread!"
|
VERY BAD
|
You shouldn't get this message...ever... If you do,
then your system doesn't allow multithreading or something weird like
that. Perhaps you're just seeing things. |
|
"Failed To Connect"
|
VERY BAD
|
Never had this error myself. If you do, I'd expect there
may be a problem with your computer. You may not have an active network
connection, or the program can't get access to it. Post on the forums
if you get this error. |
|
"Added New Bot"
|
VERY GOOD
|
Your client has received word that a new player has
joined the server. A new player in your Oblivion will be activated
and you'll begin to see him running around. |
|
"Thread Closed Succesfully"
|
GOOD
|
When you click the "Disconnect" button, if
the external thread is closed successfully, then this message will
be displayed in the external log. |
Adding
Cells
You need to have a rudimentry understanding of how to
use the CS. I'll try to make these steps as clear as possible for the
inexpereinced out there.
Not Implemented Yet (cause i'm going to go have lunch
now)
|
