Sep 28, 2017
The Adliberum Engine (ADLENGINE) - Lord Sharpe
After much testing, I determined using letters was not a good replacement for symbols so the new symbols coming in the next update for vars are:

$ = local variable

i.e.
$grillstatus=open

# = global variable
#orchealth=100

~ = private variable
~phealth=100

You will use these symbols to manipulate also.
Sep 28, 2017
The Adliberum Engine (ADLENGINE) - Lord Sharpe
After much testing, I determined using letters was not a good replacement for symbols so the new symbols coming in the next update for vars are:

$ = local variable

i.e.
$grillstatus=open

# = global variable
#orchealth=100

~ = private variable
~phealth=100

You will use these symbols to manipulate also.
The Adliberum Engine (ADLENGINE) - Lord Sharpe


First set creative mode.
creative

Next lets build an exit down.
build exit d

Now lets make the grill an exit.
build grill.exit

... and have it control the exit down.
grill.controls n

Let's make our description dynamic reflecting the changes to the grill as it happens.
room description is Before you towers a solid gate of steel, beneath and to the side a grill lies %grillstatus%

We need to make grillstatus a variable. Let's make it a local.
lgrillstatus=closed

We also need to update our status variable.
grill.if opened lgrillstatus=open grill.if closed lgrillstatus=closed

Now when you open / close the grill it will be reflected in the description as the special commands for the room name & description remain and only get processed when they are rendered.

This will also be live in the next update... coming shortly!
The Adliberum Engine (ADLENGINE) - Lord Sharpe


First set creative mode.
creative

Next lets build an exit down.
build exit d

Now lets make the grill an exit.
build grill.exit

... and have it control the exit down.
grill.controls n

Let's make our description dynamic reflecting the changes to the grill as it happens.
room description is Before you towers a solid gate of steel, beneath and to the side a grill lies %grillstatus%

We need to make grillstatus a variable. Let's make it a local.
lgrillstatus=closed

We also need to update our status variable.
grill.if opened lgrillstatus=open grill.if closed lgrillstatus=closed

Now when you open / close the grill it will be reflected in the description as the special commands for the room name & description remain and only get processed when they are rendered.

This will also be live in the next update... coming shortly!
The Adliberum Engine (ADLENGINE) - Lord Sharpe
Alongside the nomination for the #TIGAawards in the Best Roleplaying category we have the chance for #ADLENGINE to win Game Of The Year also.

To do so we need votes....

VOTE NOW at: http://tiga.org/awards/game-of-the-year

(one vote per person)

Thank you!

~ Liam
The Adliberum Engine (ADLENGINE) - Lord Sharpe
Alongside the nomination for the #TIGAawards in the Best Roleplaying category we have the chance for #ADLENGINE to win Game Of The Year also.

To do so we need votes....

VOTE NOW at: http://tiga.org/awards/game-of-the-year

(one vote per person)

Thank you!

~ Liam
The Adliberum Engine (ADLENGINE) - Lord Sharpe
MORE EXCITING NEWS!

when constructing commands you will soon be able to use surrounding %%'s to have the command lookup special values. You can use any number of them in a command and it will replace all before processing the command.

for example we could set up a variable:
gvar=hello

in our command we can then do the following:
build %var%

using the %s looks up the value against all the special properties including but not limited to:
  • local vars
  • global vars
  • private vars
  • random (value randomly rolled)
  • chosen (value randomly picked from the choice command)

You could also assign a var to player.var or target.var and then use this as a special.

Another use could be to assign special values as part of a description. For example.
lgrillstatus=closed grill.if opened lgrillstatus=open grill.if closed lgrillstatus=closed You are standing in a dungeon, a grill in the floor lies %grillstatus%

I am sure we will all be able to use this to great effect.

This will be live in the next update.
The Adliberum Engine (ADLENGINE) - Lord Sharpe
MORE EXCITING NEWS!

when constructing commands you will soon be able to use surrounding %%'s to have the command lookup special values. You can use any number of them in a command and it will replace all before processing the command.

for example we could set up a variable:
gvar=hello

in our command we can then do the following:
build %var%

using the %s looks up the value against all the special properties including but not limited to:
  • local vars
  • global vars
  • private vars
  • random (value randomly rolled)
  • chosen (value randomly picked from the choice command)

You could also assign a var to player.var or target.var and then use this as a special.

Another use could be to assign special values as part of a description. For example.
lgrillstatus=closed grill.if opened lgrillstatus=open grill.if closed lgrillstatus=closed You are standing in a dungeon, a grill in the floor lies %grillstatus%

I am sure we will all be able to use this to great effect.

This will be live in the next update.
The Adliberum Engine (ADLENGINE) - Lord Sharpe
UPDATE: CHANGE OF PLANS:
$ = local
# = global
~ = private


instead of just #
you will use $ (for local)
i.e.
$varname=100

NEW global vars:
use (#) to set a global var..
i.e.
#varname=

NEW private vars:
or (~) to set a private var...
i.e.
~varname=

This will be live in the next update!

All combinations have been confirmed working, to manipulate you would need to do:
$clockhours+timehours; #timeleft-1; ~health*roomdamage;

Just be aware that it also currently doesn't prevent you from creating duplicate variable names across each scope so its a good idea to use unique vars until I can address this issue at a later date.
The Adliberum Engine (ADLENGINE) - Lord Sharpe
UPDATE: CHANGE OF PLANS:
$ = local
# = global
~ = private


instead of just #
you will use $ (for local)
i.e.
$varname=100

NEW global vars:
use (#) to set a global var..
i.e.
#varname=

NEW private vars:
or (~) to set a private var...
i.e.
~varname=

This will be live in the next update!

All combinations have been confirmed working, to manipulate you would need to do:
$clockhours+timehours; #timeleft-1; ~health*roomdamage;

Just be aware that it also currently doesn't prevent you from creating duplicate variable names across each scope so its a good idea to use unique vars until I can address this issue at a later date.
...