Save-Point
Diablo II Waypoints - Expanded - Printable Version

+- Save-Point (https://www.save-point.org)
+-- Forum: Material Development (https://www.save-point.org/forum-8.html)
+--- Forum: Scripts Database (https://www.save-point.org/forum-39.html)
+---- Forum: RPGMaker XP (RGSS) Engine (https://www.save-point.org/forum-116.html)
+---- Thread: Diablo II Waypoints - Expanded (/thread-8076.html)



Diablo II Waypoints - Expanded - DerVVulfman - 06-16-2020

Diablo II Waypoints - Expanded
Version: 1.1



Introduction
A remastered and heavily edited version of arevulopapo's original work, this script replicates the Waypoint Travel system from Diablo II © 2000.

Like the Diablo II Waypoint Travel system, you will encounter a menu that depicts two windows. Originally, the two windows were called 'Acts' and 'Waypoints' under the auspices that the game was divided into chapters or acts. Now revised, the names within this script were altered into Regions and Locations, though the mechanics and meanings remain the same.

When properly configured, you can set events on a map that act as teleport stations, activating upon touch. Under normal circumstances, you can only teleport between such waypoints if you had encountered them before, unable to teleport to other destinations not yet reached.

Of course, a few new options have been since been added.



Script
Waypoints Page 1
Waypoints Page 2
Both scripts must be above Diablo II Waypoints - Extended as described in the script itself.


Compatibility
Designed for use with RPGMaker XP and is dependent upon two scripts as so described. Compatible with Big Maps by DerVVulfman.



Credits and Thanks
Many thanks to arevulopapo for the original system.



Terms of Use
Free for use in games, even commercial works. Only due credit for myself and arevulopapo are required.


RE: Diablo II Waypoints - Expanded - DerVVulfman - 06-18-2020

BUMP
to version 1.1

This update fixes an error.  Unfortunately, the system transported you based ONLY on your X-coordinate.   If you were to teleport to coordinate 4,15.... you'd end up in coordinate 4,4.

This bug has since been fixed.