From: Tobias Heinicke <theinicke@bss-wf.de>
To: 9front@9front.org
Subject: Re: [9front] 50$ bounty for Half-Life in 9
Date: Tue, 31 Aug 2021 19:42:17 +0200 [thread overview]
Message-ID: <63209b44-9eea-f9bd-4af4-41e9559d0225@bss-wf.de> (raw)
In-Reply-To: <CAGdRm9J=RJPd=dHhOYAdMR0VkU2Gb_PvkS3tCUdHVkOMSfMHNg@mail.gmail.com>
I think the most sane approach would be to port FTEQW (given that it is
a Quake/QuakeWorld engine and we already got qk1 and qk2 (thanks to qwx)
this may be quite feasible) and then port FreeHL:
https://github.com/eukara/freehl
That is on a quick glance: port FTEQW (probably most work), then port
Nuclide SDK (https://github.com/VeraVisions/nuclide/) (should be less
work) and get FreeHL, FreeCS and more almost for free (mostly writing
beautiful mkfiles).
Seems saner than xash3d (and also legal ; especially compared to leak
suggestion)
--
Tobias Heinicke
On 8/30/21 11:44 PM, mrowczok wrote:
> also there was a code-leak in 2003, unfortunately for your project that it
> was for hl2/hl:source
>
> https://vcc.wiki/wiki/The_2003_Leak
>
>
> pon., 30 sie 2021 o 23:42 mrowczok <mrowczok@gmail.com> napisał(a):
>>
>> also there was a code-leak in 2003, unfortunately for your project that it was for hl2/hl:source
>>
>> https://vcc.wiki/wiki/The_2003_Leak
>>
>>
>> pon., 30 sie 2021 o 21:35 an2qzavok <an2qzavok@gmail.com> napisał(a):
>>>
>>>> If you want us to port the source code, where do we even obtain the code?
>>>
>>> There's an open source GoldSource-compatible engine called Xash3D, I
>>> think it even builds on i386 Linux.
prev parent reply other threads:[~2021-08-31 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 13:53 José Miguel Sánchez García
2021-08-30 16:22 ` Elias Fleckenstein
2021-08-30 17:11 ` José Miguel Sánchez García
2021-08-30 17:12 ` an2qzavok
[not found] ` <CAGdRm9LMwEcziBO=PH5W1FVveJ_mVZxm=zG5bhez7QO3ewTNmw@mail.gmail.com>
2021-08-30 21:44 ` mrowczok
2021-08-31 17:42 ` Tobias Heinicke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63209b44-9eea-f9bd-4af4-41e9559d0225@bss-wf.de \
--to=theinicke@bss-wf.de \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).