Patching - Revision history

Kannkor at 04:11, 30 May 2023

2023-05-30T04:11:24Z

Kannkor: /* Changing between Live and Development */

2018-12-15T21:00:37Z

‎Changing between Live and Development

Kannkor at 22:11, 10 December 2018

2018-12-10T22:11:12Z

Kannkor: /* Patching */

2017-05-14T21:32:44Z

‎Patching

Kannkor: Created page with "== Patching == Patching with ISXOgre is completely automated. Every time you log in on IS1, the patcher checks every single file to ensure all the files are up to date. ===..."

2017-05-14T00:19:25Z

Created page with "== Patching == Patching with ISXOgre is completely automated. Every time you log in on IS1, the patcher checks every single file to ensure all the files are up to date. ===..."

New page

== Patching ==

Patching with ISXOgre is completely automated. Every time you log in on IS1, the patcher checks every single file to ensure all the files are up to date.

=== Changing between Live and Development ===

There are times when I develop or change some features that need more than basic testing. I push these the development server and a group of testers do some quality assurance!

There are times where a user just 'wants that feature now' and doesn't care if there could be bugs in it. Anyone is welcome to use the development server, as long as you are aware this is where features in development end up.

=== How to patch from Live to Development: ===
Load a single EQ2 session on IS1. Then in the console type:

ISXOgre:PatchDev

=== How to patch from Development to Live: ===
Load a single EQ2 session on IS1. Then in the console type:

ISXOgre:PatchLive

← Older revision		Revision as of 04:11, 30 May 2023
Line 1:		Line 1:
	== Patching ==		== Patching ==
		+
		+
		+
		+	----
		+
		+	----
		+
		+	== UPDATE! Read this! ==
		+	The development build has been removed. There was just too big of a delay between the dev build and live build, and people on both TLE and live servers wanted/needed some updates. It felt like everyone was just being pushed to development build, in which case, there is no point in having two different builds.
		+
		+
		+	Everyone that was on development build, will be automatically sent back to live build, and I will patch to live build going forward.
		+
		+	I'm keeping the below text incase this changes again in the near future.
		+
		+
		+	----
		+
		+	----
		+
		+	== Everything below this no longer applies ==

	Patching with ISXOgre is completely automated. Every time you log in on IS1, the patcher checks every single file to ensure all the files are up to date.		Patching with ISXOgre is completely automated. Every time you log in on IS1, the patcher checks every single file to ensure all the files are up to date.

@@ Line 9: / Line 9: @@
 There are times where a user just 'wants that feature now' and doesn't care if there could be bugs in it. Anyone is welcome to use the development server, as long as you are aware this is where features in development end up.
-When I release the development build to live, this means development and live are the exact same versions, it will push you back to live. This is intended. Meaning if you were wanting to test out a specific feature, when it goes live, you go back to live with it. If you want back on dev (when there is a new dev branch) you have to patch back to it. This is all intended.
+Update: It should no longer kick anyone off development build. If you wish to go back to live, use the information below.
 Note: You MUST have ISXOgre (ext isxogre) loaded before these commands will work.
 === How to patch from Live to Development: ===

← Older revision		Revision as of 22:11, 10 December 2018
Line 10:		Line 10:

	When I release the development build to live, this means development and live are the exact same versions, it will push you back to live. This is intended. Meaning if you were wanting to test out a specific feature, when it goes live, you go back to live with it. If you want back on dev (when there is a new dev branch) you have to patch back to it. This is all intended.		When I release the development build to live, this means development and live are the exact same versions, it will push you back to live. This is intended. Meaning if you were wanting to test out a specific feature, when it goes live, you go back to live with it. If you want back on dev (when there is a new dev branch) you have to patch back to it. This is all intended.
		+
		+
		+	Note: You MUST have ISXOgre (ext isxogre) loaded before these commands will work.
		+

	=== How to patch from Live to Development: ===		=== How to patch from Live to Development: ===

← Older revision		Revision as of 21:32, 14 May 2017
Line 9:		Line 9:
	There are times where a user just 'wants that feature now' and doesn't care if there could be bugs in it. Anyone is welcome to use the development server, as long as you are aware this is where features in development end up.		There are times where a user just 'wants that feature now' and doesn't care if there could be bugs in it. Anyone is welcome to use the development server, as long as you are aware this is where features in development end up.

		+	When I release the development build to live, this means development and live are the exact same versions, it will push you back to live. This is intended. Meaning if you were wanting to test out a specific feature, when it goes live, you go back to live with it. If you want back on dev (when there is a new dev branch) you have to patch back to it. This is all intended.

	=== How to patch from Live to Development: ===		=== How to patch from Live to Development: ===