vrtc / honeydew (public) (License: CC0) (since 2023-12-20) (hash sha1)
Warcraft 3: The Frozen Throne 1.27 custom scenario.
Clone URLs: https://rocketgit.com/user/vrtc/honeydew ssh://rocketgit@ssh.rocketgit.com/user/vrtc/honeydew git://git.rocketgit.com/user/vrtc/honeydew
Date (UTC) User Event
2024-04-13 04:03 vrtc Reference refs/heads/develop updated from 214594fd9b7318cfb1091f8d98cd515628c82049 to c0cd95b808528f515945084071044a92f9cb5a63
2024-04-13 03:50 vrtc Reference refs/heads/develop updated from 9d209572cdfc91684ec8fe9ed97554520d15563b to 214594fd9b7318cfb1091f8d98cd515628c82049
2024-04-12 20:03 vrtc Reference refs/heads/develop created (9d209572cdfc91684ec8fe9ed97554520d15563b)

README.md:

honeydew

This is a custom scenario for an old computer game WarCraft 3: The Frozen Throne, made by fan community of modders.

The only supported version of the game is 1.27.

Players

Players should only be interested in the map archive file, recognizeable by the file extension *.w3x. This repository contains scripts that are used to produce the complete map archive file ready to be played. These scripts themselves are not needed at runtime during play.

The complete scenario that is ready to be played or tested should be found naturally on fan websites. This repository and instructions it contains are aimed at developers first.

Developers

TODO add detailed build instructions

Instructions on how to build the project are contained in doc/build.md text file. Beside the original game itself (patch 1.27), required tools include: git, pjass, m4, smpq, make.

Source scripts for custom spells and other Jass utilities are under src/ directory. Most of these may be easily exported to other projects, without understanding the whole build process.

Copying

Everyone is free to use, modify or share this project. Text file COPYING.txt contains more details on the mode in which this project is shared.

Authors

Text file AUTHORS.txt contains list of contributions that were made explicitly for this project alone. Tools and experience employed are outside of it's scope, and are tracked entirely separately in their respective projects.

Hints:
Before first commit, do not forget to setup your git environment:
git config --global user.name "your_name_here"
git config --global user.email "your@email_here"

Clone this repository using HTTP(S):
git clone https://rocketgit.com/user/vrtc/honeydew

Clone this repository using ssh (do not forget to upload a key first):
git clone ssh://rocketgit@ssh.rocketgit.com/user/vrtc/honeydew

Clone this repository using git:
git clone git://git.rocketgit.com/user/vrtc/honeydew

You are allowed to anonymously push to this repository.
This means that your pushed commits will automatically be transformed into a merge request:
... clone the repository ...
... make some changes and some commits ...
git push origin main