View previous topic :: View next topic |
Author |
Message |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Sat Oct 08, 2011 10:47 am Post subject: TinTin++ 2.00.8 (Beta) |
|
|
Development has slowed down somewhat so I'm opening a beta thread for those wanting the latest updates and do some beta testing.
As usual the beta source code is available at:
http://tintin.sourceforge.net/download/tintin-beta.tar.gz
Changes so far:
Code: |
map.c Added terrain as a searchable option to #map list, goto, find,
and run.
map.c Added roomweight to the #map get and #map set options. By
default the weight of a room is set to 1.0 and can be anywhere
from 0.001 to 1000. The path finder will favor rooms with a low
weight.
map.c Made the layout of #map info more aesthetically pleasing and
added the listing of entrances.
substitute.c Fixed bug where functions could overwrite the original
substitution's arguments.
highlight.c Added support for xterm 256 color names, dark azure, dark ebony,
dark jade, dark lime, dark orange, dark tan, dark silver, dark
violet, light azure, light ebony, light jade, light lime, light
orange, light tan, light silver, light violet.
variables.c Added the %A #format option which prints the corresponding ASCII
value of the given character. Useful for low level string
handling.
|
|
|
Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Wed Oct 19, 2011 4:46 pm Post subject: |
|
|
Updated the beta with some new changes:
Code: |
prompt.c Added proper UTF-8 string length checking for prompt drawing.
mapper.c Room names are no longer automatically set on creation.
mapper.c Added the #map vnum command to change the current vnum.
mapper.c #map link now requires the 'both' argument for a two-way exit
to be created.
variable.c Added support to #format for %f to print floating point numbers.
variable.c Fixed color spacing bug in #format's %s handling.
|
|
|
Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Tue Oct 25, 2011 9:05 pm Post subject: |
|
|
Code: |
mapper.c Updated the fill_map routine to use breadth-first initialization
which should significantly improve execution times.
|
Last edited by Scandum on Wed Oct 26, 2011 4:52 pm; edited 1 time in total |
|
Back to top |
|
 |
Slysven
Joined: 10 Apr 2011 Posts: 375 Location: As "Jomin al'Bara" in WoTMUD or Wiltshire, UK
|
Posted: Wed Oct 26, 2011 10:15 am Post subject: |
|
|
Scandum wrote: | Code: | Code:
mapper.c Updated the fill_map routine to use breadth-first initialization
which should significantly ***increase*** execution times. |
| I hope this is a typo (or language misinterpretation)!  |
|
Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Wed Oct 26, 2011 4:53 pm Post subject: |
|
|
Yeah, that should have been improve.  |
|
Back to top |
|
 |
Slysven
Joined: 10 Apr 2011 Posts: 375 Location: As "Jomin al'Bara" in WoTMUD or Wiltshire, UK
|
Posted: Sat Nov 19, 2011 7:02 pm Post subject: |
|
|
Starting to look through the beta code and noticed that though the data infrastructure is in place for 'avoid' flag on exits the 2.00.8b4 beta happlily ignores it and will allow user through an exit that HAS been flagged as 'AVOID'.
For starters I think we need this (ignore line numbers - my source code is *modified* )
Code: | @@ -2006,6 +2681,13 @@ int follow_map(struct session *ses, char *argument)
if (exit)
{
+ if (HAS_BIT(exit->flags, EXIT_FLAG_AVOID))
+ {
+ show_message(ses, -1, "#MAP: AVOID FLAG found on EXIT:{%s}, ROOM:{%d} cannot proceed that way!", exit->name, ses->map->in_room);
+ pop_call();
+ return 0;
+ }
+
room = ses->map->in_room;
add_undo(ses, "%d %d %d", exit->vnum, room, 0); | Of course you are probably going through the route searching code as I type and you've already spotted where the tweaks will need to be made...  |
|
Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Sat Nov 19, 2011 11:55 pm Post subject: |
|
|
AVOID is only supposed to stop #map find and #map run from going through the exit.
Are you talking about manual movement? |
|
Back to top |
|
 |
Slysven
Joined: 10 Apr 2011 Posts: 375 Location: As "Jomin al'Bara" in WoTMUD or Wiltshire, UK
|
Posted: Sun Nov 20, 2011 10:42 am Post subject: |
|
|
Well, yes... It seemed like a reasonable idea!  |
|
Back to top |
|
 |
stormdragon2976
Joined: 19 Nov 2010 Posts: 73 Location: /dev/null
|
Posted: Fri Dec 09, 2011 11:49 pm Post subject: Blank lines from gagged output |
|
|
Hi,
I am still getting extra blank lines from gagged text. The text doesn't show up but everything else moves up the screen. I'm using the latest beta. Also, was wondering, is there a git repository or svn?
thanks _________________ Storm
Follow me at https://social.stormdragon.tk |
|
Back to top |
|
 |
Scandum Site Admin
Joined: 03 Dec 2004 Posts: 3844
|
Posted: Sat Dec 10, 2011 9:20 am Post subject: |
|
|
Are you sure the blank lines aren't being send by your mud?
Try #gag {^$} to gag blank lines. Some muds have a config option to send no blank lines before the prompt.
There's no repository. |
|
Back to top |
|
 |
stormdragon2976
Joined: 19 Nov 2010 Posts: 73 Location: /dev/null
|
Posted: Sat Dec 10, 2011 3:18 pm Post subject: |
|
|
Scandum wrote: | Are you sure the blank lines aren't being send by your mud?
Try #gag {^$} to gag blank lines. Some muds have a config option to send no blank lines before the prompt.
There's no repository. |
Awesome, the #gag trick seems to work.
Thanks _________________ Storm
Follow me at https://social.stormdragon.tk |
|
Back to top |
|
 |
|