Ghost hacking rooms

[Poo Bear]

Let start by making a couple of normal empty connected rooms. We'll make a room group called "normal" and add two rooms "r1" and "r2". Put in a couple of doors and connect them together, then add a player start point (an asimov) to one room. Hit shift-s to save the world and then run it to make sure it's all working.

Run the game. Check. Take a backup copy from mydocuments\mrrobot\data\user\ad000 and keep it safe.

Now create a new room group called "netspace" - it MUST be called exactly that.

Add a room to netspace called "hack1" (be careful, make sure the room goes in the right group!). We'll make it a small 10x10x10 room.

Switch to "static" components and select the "netspace" group. These are all the bits we need to make a ghost hacking room. First to do is put the floor down, use the "fill plane" button to stick a floor across the bottom of the whole room.

Then place a terminal in the middle of the floor, just sat on top. This is our point of entry/exit when playing.

Use alternating "bus" + "bridge" to make paths snaking out to nearby components. Something like this:



You can toggle F1 to switch from the normal 45deg isometric camera to straight down camera. Makes it easier to see what's going on in ghost hacking rooms.

Now go back to "r1" and add a dynamic object, the "login console". You should be prompted for a "maproom" so type in "hack1".

Don't forget to hit shift-s to save everything.

Exit the editor (or task switch away) and then open mydocuments\mrrobot\data\user\ad000\ folder where this new level is stored. Note that if you've made other uder adventures already it might called ad001 or ad002, etc.

Open the games.config file and change the line called roomgroups so it reads "roomgroups 1,2". This lets the game know it should loading roomgroup 1 "normal" and roomgroup2 "netspace". Save it out.

Now find a folder in mydocuments\mrrobot\data\user\ad000\ or wherever it's been saved, called "ghost". Inside there should be a folder called "maps". In here create a text file called "hack1.config". Here you will setup what kind of battles and loot are to be found.

This example is from late in MrRobot. The loot section describes things you might find, being a late ghost hack there is all kinds of powerful loot in this hack.

[Crussh]

Nice, but the game explodes when i try to start the hack >__<

[Poo Bear]

Doh! I kind of suspected you'd say that, making ghost hacks isn't that user friendly.

Unless I've forgotten something it should have worked.

Here are the files I made all inside an "ad000" folder, remember, if you've already got some folders in there extract this somewhere else and put it in the next free folder i.e. "ad001",etc.


http://www.moonpod.com/board/images/misc/ad000.zip


It definitely works for me - honest

[Blizgerg]

First off I have to take a moment to express my feelings on the subject of finding out how to make a ghost hack.

YAY!!!!!! YAY!~!!!!

Now that that is out of the way...

I downloaded the zip file and tested it out and it seemed to work fine.
Now to start playing with this new information!

[Crussh]

Maybe it has something to do that my computer cant open web configuration files? Your adventure worked but the ghost hack was impossible.

[Blizgerg]

I would like to ask for a list of all enemies names and loot names that you can place in the ghost hack config file. I have already come up with a list of some of the names of the stuff that you can put into the lockers but I know it isn't complete. I was able to guess all these with a little help from a hex viewer.

I was able to figure out that the little scramblers are called SCRAMBLER_GRUB.

I'll go ahead and paist my list here:

[Poo Bear]

I've edited your list, which was almost complete really.

[Dotz]

you should put notes that say the name of each item/enemy. unless its obvious.

I find this kinda user unfriendly. It's like, you make a level, then you make the netspace, then you make the hacks (it's fine) but at this point it gets odd. then you have to close the editor(save) and open a txt document, and type in all of the code of each enemy you encounter, what rewards you get, and other stuff. Then you have to use some sort of parameter thing to get it to detect the hack.

This kinda stuff always makes me wonder if anyone can use the user unfriendly stuff (like C++)

[Poo Bear]

Yeh, sorry it was for our own use really and then it kind of escaped into the world at large

[Zanpakuto]

[Poo Bear]

The thing I always say to people is to start simple, no, simpler than that, really simple. Make something so simple it can't possibly fail to work, then back that up and make something a bit more complex. After 4 or 5 maps you'll be more familiar with what works and what doesn't.

I'll just go and remind myself how it all works

[Poo Bear]

I think the ****** config file loader is getting confused by all the trailing spaces in the hack1.config

Open it in notepad, check each line of text doesn't have any spaces on the end, just delete them.

To make a successful hack open a door means writing lua scripts and checking in them to see if you met the objective. I can go through and work up an example if you get that far.

[Zanpakuto]

[Poo Bear]

Sorry it's awkward, these tools were made for me to make the game and only got released by popular demand. They should really have been made easier to use. Anyway...

You can add lines to specify what treasure will drop:
loot0 1,80
loot1 4,10
loot2 6,5
loot3 9,5
etc

The two numbers that follow 'loot0' identify the bit of loot to drop and the probability of it dropping. So 'loot0 0,100' would mean that if you win the fight then you will ALWAYS get loot item 0 (the first item of loot specified at the start of the file.

Here is an example that always causes a battle to start whenever you cross a 'RAM' module. Note 'probability 100' means a fight always starts with a SCRAMBLER. If you win this fight there is an 80% chance you will get loot item 3 and 4 as a reward, remember that refers to the list of all loot at the top of the file.

Example:

[Zanpakuto]