Table of Contents
Welcome to James Kemp's Wiki
This is a collaborative web platform that allows people to edit1) the web pages to provide additional content for some of the stories I have written and the roleplaying games that I am involved in, whether as a player or GM.
There are several namespaces operating slightly different wiki subjects. These are, in no particular order:
- Skyss - Story Background - a fantasy novel I wrote for NaNoWriMo 2016.
- Perfects - background for the near future story and some police roleplaying that I ran in that universe
- Theocracy of Daprav - A D&D campaign that I ran with Glasgow University Games Society around 2002-3.
- Jim Wallman's Universe - a roleplaying by e-mail campaign that I play in, this is an unofficial wiki and none of it is canon unless Jim says it is.
- Interstellar Freelance Unlimited - subset of the Universe pages covering the activities of a mercenary company that we are currently roleplaying every Full Moon.
- Earth Imperium pages. These cover the activities of the Government of the Solar republic (aka Earth Empire) in Jim's Humanity Will Prevail campaign, including the Earth Imperium News Items.
- Free Worlds Alliance - covering the activities of another emerging polity in the Humanity Will Prevail campaign. Mostly contributed by Eric Moroney.
- Universe Background - page collecting the various bits of background info that have come up in various e-mail discussions for the campaigns set in Jim Wallman's Universe.
- Master map of the Universe (6Mb PDF, as at 3212).
- Delta Green - some roleplaying campaigns about horror and conspiracy. The main one was set in Berlin in 1953.
- Free games rules - a collection of free rules for wargames and other sorts of face to face games that I have designed or run.
- Wargames rules - I'm not just a player of games, I also do rules for them from time to time as well as one-off games. A primary outlet for this is through Chestnut Lodge Wargames Group.
- Other free rules - at the moment just those for the 1689 (Orange or Lemon? and Bonnie Dundee, respectively about the debates in the Scots Parliament and then the military campaign of Viscount Dundee during 1689) and The Other Side of the COIN (about what makes people become insurgents). All games that I have have produced for Chestnut Lodge Wargames Group.
- Background for a near future universe where I have written some fiction and also run some roleplaying games in.
Comments and complaints to me at webmaster@full-moon.info please.
James Kemp
Tag Cloud
Recent Additions
Lakshmi Background
ANy info we find relevant needs to go here.
- Mukul has the hard copy list
Clewgist Temple, Goof Ball
This was a training mission to bolster security for a Clewgist temple on Goof Ball. This was a misxture of straight training and security advice to ensure that the temple could deal with any sectarian violence that they believed might occur.
Specific Customer Requirements
Improve acolyte weapon skills
There were lots of simulations in the temple and we recommended stepping up the use of simulations for weapons training. We also took each acolyte out to the farm for a day or so to do some actual live firing (no matter how good simulations are nothing is the same as actual live firing to get a feel for the weapon).
Tactical training
Ditto with the weapon skills. However we also identified a number of the temple staff and acolytes to give the equivalent of an NCO cadre to so that they had a more thorough understanding of tactics and employment of weapons as well as (more importantly) the necessary skills in methods of instruction so that they could be effective instructors of other acolytes or novices.
We also ran a series of simulations on situations related to attacks on the locality to train them in the drills required in the event of nearby unpleasantness.
Improve the active and passive defences of Temple
There were three basic attacks that we were defending against:
- bomb blast;
- individual infiltration; and
- mass assault.
In terms of the last we noted that the police were reluctant to react but that there was a limit to what they could ignore.
There were specific risks in terms of vehicle bombs being parked outside or attempting to drive through the compound walls, flyers dropping bombs or crashing, infiltration via the sewer systems or nearby. There was also the possibility that a lone gunman or bomber would come through the front gate in a group of others.
The sewers were already blocked and watched satisfactorily and we didn't see any need to enhance this further.
There were also good relations with the owners/users of the several small warehouses at the back and this was felt by the High Priest to be a most effective preventative against that being used to place a large bomb (or any other threat) against the Northern wall of the temple.
To prevent successful infiltration we recommended turning the temple into a secure access zone with biometric controlled access backed up with CCTV cameras and other observation devices to ensure that there was a firm record of who went where and when and that people only went where they were specifically authorised to do so. Also this was enforced with a permanent guard presence and a QRF with access to legally held weapons just in case.
Improved resilience of the compound was also recommended by
- adding 20 feet of chicken wire on top of the 10 foot concrete wall. This to be reinforced by razor wire and sensors on the outside so that there would be no chance of it being climbed without warning. The additional height could also help stop rocket attack from the Victory Hab Block which otherwise overlooked the temple site.
- Primary power by multiple small generators all linked to the grid with underground storage tanks with a week's worth of fuel. Secondary power could come from the local grid with a last resort of battery power giving up to an hour of active time for all essential systems (including lighting and ventilation as well as for security systems). It was felt that any incident causing dissociation from the grid and loss of primary power would be over within an hour.
- The concrete wall should be reinforced to stop ground vehicle attack by adding bollards at the pavement edge (some six feet from the wall) round the outside of the temple compound. Some reinforcing of the Eastern & Western walls was also recommended and the closing up of the service access in the Eastern wall.
- No vehicles (except those owned by the temple) should be permitted inside the temple compound. Most of the followers lived across the main road so there was little use of the car park. Instead the current vehicle park becomes a sterile area that provides some blast precautions and also home to an armoured vehicle owned by the temple that could be used in a last resort to force an exit.
- The inner compound should be subdivided by means of some barricades and shelters to ensure that people who enter don't have free access to the entire temple (not doing this would undermine the secure entry system).
- Every building should have a blast and fire shelter that would protect the occupants from explosions and fires within the building. These should be stocked in advance with food, water and weapons in case they were required in the event of a direct attack on the temple.
- In particular the acolytes accommodation nearest the Eastern wall should be used less for sleeping as it was deemed to be too close to the outside wall.
- All buildings should have their windows treated and other suitable bomb blast precautions taken to minimise the damage caused in the event of an explosive device being detonated. Detailed specific advice on this can be supplied on request.
- All temple staff need to be briefed regularly on the security situation and how they need to behave in a secure zone. They also need some specific training in security procedures
Outside the temple complex we also did some work.
- cameras were installed on the Colony Hope Estates to monitor comings and goings from the Satanist meeting house so that tabs could be kept on who was visiting the site.
- sensors were installed on the rooftops of the CH Estate to monitor flyer traffic (a combination of comms traffic and visuals).
- a QRF base was established for when the risk of flyer attack was thought to be high to take up position on the top of the Northern most block on the CH Estate to fire upon any flyer that attempted to attack the temple with whatever weapons the priests had that they thought might be effective. [IFU - we didn't think that the priests could have any
legally held weapons that might be effective, but if trying to shoot down a flyer with a hunting rifle made them feel safer that was their business, there was plenty of simulator time to practice.]
Plan for defence of co-religionists in CH Estate
Several plans were worked up for Clewgist Lawful Assistance to the Population (CLAP) which were run through the simulators as part of the weapons and tactical training. This ranged from small scale action largely unarmed to some riot training (in the role that the police normally take as opposed to teaching them how to riot). We also covered various drills using legal weapons.
Purely for fun and diversion we also gave them some scenarios for their Whole-Life[TM] Simulation engine on hostage rescue using GF weapons and assault rifles. This was purely an academic exercise for the further enlightenment of the acolytes who sought a greater understanding.
Our main recommendation though for increasing the safety of the Clewgists on the CH estate was to try and avoid confrontation and to reduce tensions between the various religious factions by not provoking each other. An example of this was the route home of the Satanists which took the long way round the CH Estate singing inflammatory songs (The Dress Your Father Wore being but one such example). This was not helped by the 20 Clewgist acolytes standing outside the temple ready for the fight when the Satanists marched past. If nothing else our tactical training and camera emplacements should allow the Clewgists to
- gain tactical surprise;
- produce evidence that the Satanists started it; and
- win the fight with minimum casualties.
Applicants
<php> $ad=2; $loc=8; $time=20;
echo “AD = $ad \n Location = $loc \n Time = $time \n\n<br><br>”; if ($ad == 1)
{
$cost = 1.5 * $time;
if ($time == 30)
{
$ads = 2;
}
$ads = 1;
}
if ($ad == 2)
{
$cost = 5 * $time;
if ($time == 10)
{
$ads = 2;
}
$ads = 3;
}
if ($ad == 4)
{
$cost = 25 * $time;
$ads = $ad + ($time/10-1);
}
$d6 = rand (1,6); $apps = $d6 * $ads * $loc; echo “<b>Number of Applicants ($apps)</b> = Recruiting score for Advertising ($ads) x Location Score ($loc) x 1d6 ($d6).”; echo “<br>\n
Recruitment cost $cost credits<br>";
echo ”<h2>Applicant Details</h2> \n
\n
<table width = 85% cellpadding = 1>\n
<tr> \n
<td>App \n
<td>Firstname \n
<td>Surname \n
<td>Gender \n
<td>Genetics \n
<td>References \n
<td>CR Check \n
<td>Experience \n
<td>Interview? \n
<td>Hire? \n
</tr>";
$appl=1; do
{
$CrimCheck=rand(0,9);
$Experience=rand(0,9);
$RefCheck=rand(0,9);
$Gender=rand(0,9);
$BirthGender=$Gender;
$GenderChanged="No";
if($Gender==0)
{
$GenderChanged="Yes";
$BirthGender=rand(1,8);
$Gender=rand(1,8);
}
if($Gender==9)
{
$BirthGender=rand(1,8);
}
if($Gender<5)
{ $sex="M"; }
elseif($Gender<9)
{ $sex="F"; }
elseif($BirthGender<5)
{ $sex="M"; }
else
{ $sex="F"; }
$Genetics="Natural";
$gen=rand(1,6);
if($Experience>8)
{ $Genetics="Perfect"; }
elseif($gen>4)
{ $Genetics="Perfect"; }
connect to MySQL server and select the IFU database include (“/var/www/html/IFU/sqlconnect.php”); include (“/var/www/html/IFU/sqlconnect2.php”); $db = mysql_select_db('full-moon_info_-_IFU',$connection); randomly select a group of names from the database $sql = 'SELECT * FROM `Names` ORDER BY Rand() LIMIT 10'; $names = mysql_query($sql);
step through the selected list of names to get a surname and forename from separate rows while ($row=mysql_fetch_array($names,MYSQL_ASSOC)) { extract($row); $LastName = $Surname; next($row); then randomly take a firstname of the correct gender from the same list
if ($Gender==$sex)
{
$Forename = $FirstName;
next($row);
extract($row);
end($row);
}
}
echo “
<tr> \n
<td>$appl \n
<td>$seed2 $FirstName \n
<td>$seed1 $Surname \n
<td>$sex \n
<td>$Genetics \n
<td>$RefCheck \n
<td>$CrimCheck \n
<td>$Experience \n
<td>Interview? \n
<td>Hire? \n
</tr>";
$appl++; } while ($appl⇐$apps); echo ”</table>“; </php>
OOC Some of you will already know that the Sirian team, Jurrien de Jong, has sent along a robot as one of the scientists on the 'BOLDLY GO' deep space mission. Below is the correspondence between the Earther admin [played by me at the moment] and Jurrien.
Subject: Boldly Go Science Team on IEN Odyssey - Mr A. Steel
CONFIDENTIAL
BOLDLY GO MISSION ADMINISTRATION
To The Sirian Government [citizenship law section]
From 'Boldly Go' office, Human Resources Division
Dear Sir, Madam or Robot,
'Mr Archie Steel', a robot described as a 'Sirian Citizen' on its SSR entry documentation, is to be entered by me on to the ship's books of the IEN vessel Odyssey. I wonder if you could help me clear up a few minor technical points?
1. What sex is 'Mr Steel' considered to be? Is 'he' male, having a Y-chromosome, or, as it is a machine, neuter?
2. What is considered to be Mr Steel's 'date of birth' for the purposes of calculating its age? Is it the date it was switched on? If it is switched off and on again, does its 'birth' recur?
3. If 'Mr Steel' is damaged or destroyed, rendered 'dead', whether accidentally or deliberately, what will be the legal position from the point of view of the SSR? You will understand the difficulty; [as, according to our Legal Dept.] while aboard a Solar Republic vessel where Solar Law applies, 'Mr Steel' is considered to be an object, however complex and expensive, and not a human person, nor an animal where anti-cruelty laws would apply, and therefore only the laws against criminal damage protect it.
If your understanding is different on any of these points, please let me know.
I remain, Sir, Madam or Machine,
Your Obedient Servant,
[illegible squiggle] HUMAN RESOURCES Division
Reply from SSR Citizenship Section
Dear Sir,
Mr Archibald Steel is indeed a Sirian citizen, his citizenship being granted under the Naturalisation Act, clause 23.b.27f. Mr Steel's personalia are as follows:
Archibald Sakhumvit mBebe Steel III, male, born 291-3183 at Suvorov Scientific Compound, Conqueror 7.
Mr. Steel, to all intents and purposes, is a male and should for all matters of supply and social contact be treated as a male. However, Mr Steel seems to be quite capable to speak up for himself, should he consider himself to be mistreated (but you didn't hear this from me)
We do understand your problems with the 'age' of mr Steel. 291-3183 can be taken as the date at which his keel was laid (pardon my English), as Mr. Steel himself would have it. Since then mr Steel has alway been terribly 'switched on', although at certain times his main CPU has been off line due to renovation. In all those cases the secondary CPU has been active, so mr Steel was fully conscious, to use a limited analogy.
To all intents and purposes, mr Steel is a human being, as you will understand when experiencing his proximity. It was never the choice of the SSR to have its personnel under the command of Earther officers or on Earther ships, but we have indicated at an earlier stage that the Sirian citizens on the mission would do so not under SSR authority but on their own account. Although the government of the Earther Empire has acnowledged its breach of the New London treaty and made a partial apology, the SSR sticks to this arrangement until full satisfaction on this issue has been achieved. The Sirian members of the mission are thus not protected by their Sirian citizenship. Under other conditions the SSR government would have certainly affirmed its 'property rights' on mr Steel. Mr Steel accompanies the mission on his own accord and thus should accept the conditions you set. Let me just advice you that mr Steel will react in self-defence when threatened with cruelty (both physically and orally). He leaves a trail of broken hearts…
I hope this answers your questions
regards
Aïsha Ben Hemmed IV
Senior Person Responsible
BOLDLY GO MISSION ADMINISTRATION
SIRIAN CITIZEN MR A. STEEL
Dear Mr IV,
Thank you for your prompt and helpful response. Mr Steel will be entered onto the ship's books as a Sirian male citizen, aged 19. His achievements for that age are certainly formidable. Your acceptance that Mr Steel will have only the protection of Solar Republic property law is noted and the Mission Commander will be informed.
I remain, Sir,
Your Obedient Servant,
[illegible squiggle]
HUMAN RESOURCES DIVISION
