Skip to content

Latest commit

 

History

History
36 lines (17 loc) · 3.03 KB

README.md

File metadata and controls

36 lines (17 loc) · 3.03 KB

RS317.Sharp

A fork of 317Refactor that is ported to C#/.NET.

Special thanks to the developer of RS2Sharp which indirectly contributed to the WinForms/GDI rendering and input code.

Implementations

Rs317.Sharp is made up of the core Library of the RS engine as well as some code that allows for easily creating implementations of the client. Currently, two implementations exist.

Rs317.Client.WF: Is the Winforms/GDI+ implementation that renders similarly to the Java applet version by pushing bitmaps to the screen.

Rs317.Client.OpenTK: Is the OpenGL/OpenTK implementation that also, as of the time of this documentation, pushes bitmaps to the screen via OpenGL. However, because it's GPU rendered it allows for psuedo-antialiasing and Resizable. Eventually it should/could support rendering the gameview as OpenGL meshes.

Rs317.Client.Unity3D: Is the Unity3D implementation. It has similar feature set as the OpenTK client including resizeable mode and psuedo-antialiasing. It does not yet support rendering 3D.

FAQ

Q. Why isn't my Cache loading?

A. Unlike most clients, this client expects the cache to be in a subfolder called Cache.

License

Applicable licensing referenced in 317Refactor and additional work/changes done licensed under a modified AGPL 3.0 licensed.

Contributing

What does modified mean? Well, the APGL cannot be modified. In this case, I'm just refering to how contributions work. Any contributor to the project retains an additional unrestricted, non-exclusive, perpetual, and irrevocable license granted to themselves for all portions of work they contribute.

What this means is if you write something, contribute it as a pull request to the repository, it is licensed to other users under AGPL 3.0 but you also retain your ownership and rights to it too, so you can do whatever you want with the code you've written yourself and aren't restrited by the repositories AGPL license. In the plainest of terms, you can do whatever you want with what you write. Just not with what everyone else has written, which requires you to follow the AGPL.

Why? Well, every project should define contribution licensing. Just because a repository is licensed under a particular license does not mean automatically pull-requests are. It's just not how copyright works! So, projects like Microsoft's Corefx require contribution to be under a particular license. This project just requires you license your contributions under the same repository's AGPL 3.0 but that you also essentially retain the ownership to your contribution at the same time.