Carrying over Map Information?

[Tronovision]

I was not sure if this should have been posted under UScript or UEd, however it likely involves both, so here we go:

Is it possible to carry information about the state of triggers, events, etc. from one map to the next? For example, lets say you have to back to the previous level to access a passage that was inaccessable at the time (e.g. rocks were blocking it), however after a siezmic event (in the current level) the passage is now passable (i.e. the rocks have moved).
I realize that you could also acheive this effect by creating duplicate maps with these changes made (i.e. map 1a - rocks in the way --> map 2 --> map 1b - rocks not in way), but in some situations it may be much more efficient to use the same maps but with altered states and events. Anyone know if/how this can be done?

Cheers!

[Chaos13]

It is possible by using a configuration object. For example:
There is object PassageRocker in package MyPassageRocker:

Code: Select all

class PassageRocker extends Actor config(PassageRocker);
var config bool bMoveRock;

event PostBeginPlay()
{
local Actor A;
super.PostBeginPlay();
if (Left(String(Name),InStr(String(Name),".")~="MyPassageLevelName")
if (bMoveRock)
{
foreach AllActors(class'Actor',A,'TagOfMyRock')
A.Destroy();
bMoveRock=False;
SaveConfig();
}
Destroy();
}

The trigger should be like in same package and look like:

Code: Select all

class PRTrigger extends Triggers;
event Touch(actor Other)
{
local PassageRocker Temp;
if (Other.IsA('PlayerPawn'))
{
Temp=Spawn(class'PassageRocker');
Temp.bMoveRock=True;
Temp.SaveConfig();
Temp.Destroy();
}
}

havent tested, written code quickly in-the-forum editing box, not checked for working, but should work.

Please do not name your actors like this and use the code directly you need to make big modifications to it.

[Tronovision]

Thanks! Is it the "SaveConfig()" command that temporarily holds the information? Cheers!

[Chaos13]

[glow=yellow,2,300]Warning: it must be var CONFIG bool bMoveRock;[/glow]

Well, its quite more complicated. The ini configuration is being modified and saved by the trigger. To save the configuration you need to do SaveConfig(); Configuration is loaded when actor is spawned. Configuration is saved in ini file, so it is not affected by server restarts \ map switches \ etc.

[Tronovision]

I see... This would make it easy to cheat by editing the ini file, would it not? I don't suppose that you could have this information stored in a savegame file (which may be a bit more cryptic and harder to manipulate than an ini configuration file)... No worries if it cannot, but just wondering though.

[Chaos13]

You can cheat by ghosting then btw.

[GreatEmerald]

You can do it the UBeta way - make the player appear in another place back to map 1, directly above a trigger. The trigger will do what you want, open the passage for the player and close the doors to the map 2.

[Tronovision]

You can cheat by ghosting then btw.

Ya, you'r right. If people want to cheat, they will!

I'll try building a map to see if I can get this to work. Cheers!

GreatEmerald:
Also a good suggestion, thanks!

[Chaos13]

GreatEmerald grant me great idea... You can create special teleporter class with special Accept() \ Touch() functions that will do what you want however you can cheat by typing open MapName#teleportertag (in online gameplay too )