Editor 1.1.20 hotfix

[Rudankort]

Hello All!

The Editor in 1.1.20 has problems loading some scenarios which it previously saved. The problem is related to load code, so scenario files themselves are not corrupted, but still it is a major issue. Until a proper fix is released together with the next patch, you can download the fixed Editor EXE here:
https://www.dropbox.com/s/2nd5f5x4qoibp ... r.exe?dl=0

Let me know if you still have any issues with this fixed version.

[KaiP]

Thanks you - but my scenario want load any more after change the unit camo with the old editor - 3 days work lost. I changed the written row with the old editor with uniform camo manually in text editor to my old file - and now it no more start.

I accept that and rework this scenario from the beginning, if you answer two questions please !
1. How can I give an spawned unit a name in Lua Script ?
2. How can I set the unit uniform camo for swawned units in Lua Script ? Normally they come all with default settings.

[asuser]

Thanks for fast help but...

I downloaded the hotfix and put it in the main directory (Steam version). After execution, a new error message appears:
"HTMLayout.dll could not be found"

Did I use that wrong?

[jeannot le lapin]

Thanks for fast help but...

I downloaded the hotfix and put it in the main directory (Steam version). After execution, a new error message appears:
"HTMLayout.dll could not be found"

Did I use that wrong?

PzC2Editor.exe to the wrong place

No problem for me :

Editor.JPG (45.3 KiB) Viewed 8563 times

[asuser]

Oh, now it works!

Thanks, you are (both) my heroes of the day!

[Rudankort]

Thanks you - but my scenario want load any more after change the unit camo with the old editor - 3 days work lost. I changed the written row with the old editor with uniform camo manually in text editor to my old file - and now it no more start.

I don't quite understand from your description what happened there, but if you give me your pz2scn file, I'll take a look.

[n0b0dy007]

A feature request for the editor, to help with scripting the associated Lua file:

An export to text file of the expected condition and effect functions.
For example, from the Seville.pz2scn scenario, something like:

Code: Select all

-- 3 Objectives defined in scenario:
	-- @end	Capture victory hexes	Cadiz (7;24) and Seville Airfield (10;14)
	-- opt	Hold victory hexes		Auxiliary Airfield (9;8)
	-- opt	Custom objective		CustomSuccess2() | CustomFail2()

-- 7 Triggers defined in scenario:
	-- 1x	StartGame(NewRoundAction)		{if AlwaysTrue()}		-> OnStartGame()
	-- 1x	EnemyHero(NewRoundAction)
	-- 1x	Objective1(ObjectiveStatusAction)	{if Objective1Condition()}	-> OnObjective1()
	-- 1x	StartTurn4Message(StartTurnAction)	{if Turn4MessageCondition()}	-> Turn4MessageEffect()
	--	OnNewRound(NewRoundAction)		{if EmptyCondition()}
	-- 	CaptureAF(CaptureFlagAction)						-> OnCaptureAF()
	-- 	Village(CaptureFlagAction)						-> OnCaptureVillage()

Even better would be to export function skeletons in Lua format, with the above info as function comments.