Difference between revisions of "User:Demolishun"

From the Oblivion ConstructionSet Wiki
Jump to navigation Jump to search
imported>Demolishun
imported>Demolishun
Line 29: Line 29:


Let me be clear on the scope of the plugin.
Let me be clear on the scope of the plugin.
* It will provide access to the local machine by providing a UDP port on the 127.0.0.1 port.
* It will provide access to the local machine by providing a UDP port on the 127.0.0.1 address.
* It will NOT have any kind of security features.
* It will NOT have any kind of security features.
* I do not recommend allowing external programs to access the UDP port.  Firewall it off and only allow programs on the local machine to access the port.
* I do not recommend allowing external machines to access the UDP port.  Firewall it off and only allow programs on the local machine to access the port.
* Use a program to access the port on the same machine that provides any services for getting data external to the machine.  This means use a program that is designed with security in mind and can handle possible external attacks to the machine.
* Use a program to access the port on the same machine that provides any services for getting data external to the machine.  This means use a program that is designed with security in mind and can handle possible external attacks to the machine.
* Using this approach keeps the code in the plugin very simple and robust.  It will do whatever it does very well and nothing else.  Otherwise you end up never finishing and have a buggy implementation nobody can use.
* Using this approach keeps the code in the plugin very simple and robust.  It will do whatever it does very well and nothing else.  Otherwise you end up never finishing and have a buggy implementation nobody can use.

Revision as of 01:26, 15 June 2012

What I am working on...

I am working on a plugin for OBSE. It will allow UDP communication between Oblivion and an external app. The plugin will allow for data to be converted to and from JSON messages that will convert to and from oblivion objects. It will also have the ability to launch an external app to connect to the engine and handle more advanced processes like databases, remote resources, and other tasks. The plugin will just be a transport. That will be the scope of the interface. This should allow modders to add significant functionality to the engine without extraneous features.

I am using the boost framework to get a reliable networking code base. I am also using a very mature JSON library to handle parsing of data both to and from the engine. I have just finished the parser and am testing it. I have simple UDP up and running in a thread and I can send and receive data to the engine.

Notes: In order to convert a FormID or RefID number I needed to build a TESForm and set the ID against it. So this is the code needed to do so if you have the ID:

UInt32 tref;
g_serialization->ResolveRefID(tint,&tref);
TESForm *formref = LookupFormByID((UInt32)tref);

Demolishun 16:32, 14 June 2012 (EDT)


Wild ideas:

Implementing logic outside the engine using Python.

Current feature being worked on:

Plugin for OBSE to realize the stuff I want to do.

  • Plugin for network access.
  • Use plugin to attach to external resources through Python.
  • Ability to store objects and restore them, or even create new objects.
  • Potential for a master server run by groups of individuals to do actual pen and paper role play through the engine. Note: I am NOT going to write this. I am going to provides the tools so someone else can.
  • Pull data off of websites to affect content in the game.
  • Use a database to store relational data that can be persistent between games/characters. You could potentially use it to meet up with your other character somewhere in the game world. This could also be used to add persistent gameworld features.
  • Create plugins that store items that you can access by other players.
  • Control the game externally.

Let me be clear on the scope of the plugin.

  • It will provide access to the local machine by providing a UDP port on the 127.0.0.1 address.
  • It will NOT have any kind of security features.
  • I do not recommend allowing external machines to access the UDP port. Firewall it off and only allow programs on the local machine to access the port.
  • Use a program to access the port on the same machine that provides any services for getting data external to the machine. This means use a program that is designed with security in mind and can handle possible external attacks to the machine.
  • Using this approach keeps the code in the plugin very simple and robust. It will do whatever it does very well and nothing else. Otherwise you end up never finishing and have a buggy implementation nobody can use.
  • KISS is the approach I am taking: Keep It Simple Stupid. Less is more.

Things I would like to see in OBSE 21

Animation triggers that can be tied to events like Sound keys.